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

Automated cherry pick of #105: Management blueprint; add kptfile and use workload identity #109: Update instructions for using ACM. #113: ACM: notebook controller needs to use istio ingress Cherry pick of #105 #109 #113 on v1.1-branch. #105: Management blueprint; add kptfile and use workload identity #109: Update instructions for using ACM. #113: ACM: notebook controller needs to use istio ingress #122

Conversation

jlewi
Copy link
Contributor

@jlewi jlewi commented Aug 12, 2020

Related to: #118

Cherry-pick some fixes for the management blueprint onto the 1.1 branch

Jeremy Lewi added 3 commits August 12, 2020 06:52
…CNRM

* management/instance needs a Kptfile to work with the latest versions of kpt

* Per GoogleCloudPlatform#13 we don't want to run CNRM in namespace mode because this burdensome
  instead we use workload identity mode; i.e. the same GCP sa to administer
  multiple projects.

Related to GoogleCloudPlatform#13 - Use workload identity mode
Related to GoogleCloudPlatform#102 Fix blueprint

* Remove cluster and nodepool patches from instance; we aren't actually patching anything.
* Use a kpt function to remove namespace from non namespace scoped
  objects

* Use yq to attach backend config to the ingress.

* Remove the iap enabler pod; this is a partial work around for GoogleCloudPlatform#14

  * The IAP enabler pod will try to update the ISTIO security policy
    which will conflict with ACM. So we disable it for now even though
    that means we have to manually update the health check.

* Switch to using a structured repo with ACM (GoogleCloudPlatform#29)

  * Add a script to rewrite the YAML files in the appropriate structure

  * If we don't use a structured repository we end up with problems because
    resources in different namespaces but with the same name will be written
    to the same file.

* Add a hack to create the kube-system namespace as part of the ACM deployment.

  * Now that we are using structured repositories we need to have
    a namespace directory with a namespace.yaml for kube-system
    in order to install resources in that namespace.

Related to GoogleCloudPlatform#4 - use ACM to deploy Kubeflow
@k8s-ci-robot k8s-ci-robot requested review from Bobgy and rmgogogo August 12, 2020 13:53
@kubeflow-bot
Copy link

This change is Reviewable

@jlewi
Copy link
Contributor Author

jlewi commented Aug 12, 2020

/test all

@jlewi
Copy link
Contributor Author

jlewi commented Aug 12, 2020

Test failure looks like some problem getting credentials to submit the Tekton run.

@Bobgy
Copy link
Contributor

Bobgy commented Aug 13, 2020

/lgtm
/approve

@k8s-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Bobgy

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 37012dc into GoogleCloudPlatform:v1.1-branch Aug 13, 2020
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