Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix hard coded "name" variable in example prototypes #1013

Merged
merged 1 commit into from
Jun 16, 2018

Conversation

xyhuang
Copy link
Member

@xyhuang xyhuang commented Jun 16, 2018

This fixes the hard coded "name" variable in the example prototypes so that it can take the value from exposed parameters and be compatible with the user guide.

The other hard coded variables remain as-is to keep it simple. However they could also be modified in the same way, if needed.


This change is Reviewable

This fixes the hard coded "name" variable in the example prototypes
so that it can take the value from parameters.
@ddutta
Copy link
Member

ddutta commented Jun 16, 2018

/ok-to-test

@ankushagarwal
Copy link
Contributor

/lgtm
/approve

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ankushagarwal

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot merged commit 0726d43 into kubeflow:master Jun 16, 2018
saffaalvi pushed a commit to StatCan/kubeflow that referenced this pull request Feb 11, 2021
This fixes the hard coded "name" variable in the example prototypes
so that it can take the value from parameters.
yanniszark pushed a commit to arrikto/kubeflow that referenced this pull request Feb 15, 2021
surajkota pushed a commit to surajkota/kubeflow that referenced this pull request Jun 13, 2022
* Use a configmap generator for the spawner_ui_config.yaml

* Using a configmap generator is a bit cleaner because we can store
  the configuration file in a external file rather than inlining it in
  the config map.

* Using a configmap generator also has the advantage that kustomize will
  generate a unique name based on a hash of the content.

  * This has the advantage that if a user updates the config, the hash
    would change so deployments would automatically be redeployed in order
    to pick up the config changes.

* Also update the default image used in the configmap to fix kubeflow#1010

* Rebase and regenerate the tests.

* * The deployment for the UI needs to use the original name of
  the jupyter web app config map without the prefix/suffix.

* Update expected tests.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants