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
Kubernetes API server removed support for the root /proxy paths in v1.10 (deprecated since v1.2) #1398
Comments
@Ark-kun What URls in Kubeflow are using /proxy? |
I've seen many swagger files mentioning the deprecated /proxy URLs. The GitHub search does not turn them out now for some reason. |
@Ark-kun Which README.md? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
/reopen |
@Ark-kun: Reopened this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@Ark-kun this issue / request seems old. Is there an another path to build and support the needed environment? |
* Convert v1 to v2 setters & substituions in gcp * The latest version of kpt started choking on gcp/v2 because we were still using the old style setters and substitutions. * This PR creates a kptfile to use the new setter and substitutions. * hack/create_kptfile.py contains a script to generate lot of the setters and substitutions. * kf-vm-sa.yaml shouldn't specify the namespace; this will get set in an overlay * Move workload identity bindings for kf-admin KSA from kubeflow/instance in gcp blueprints repo into this repository. related to gcp-blueprints#89 * Fix image mirror substitution. * Create a KptFile for stacks. * Add conversion for stacks. * Add KptFile for stacks/gcp
See kubernetes/kubernetes#59884, kubernetes/kubernetes@687c651, kubernetes/kubernetes#59885,
We'll need to fix our URLs otherwise they would stop working once we upgrade to 1.10.
The text was updated successfully, but these errors were encountered: