V1.2 branch #36
Merged
V1.2 branch #36
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ranches (kubeflow#4665) * WIP Updated website versioning for new banner on archived doc branches. * Updating website instructions while testing. * Further clarified instructions after testing the process. * Fixed typo.
* The infrastructure for continuously rebuilding our docker images and updating our kustomize manifests has now been generalized. see kubeflow/testing#450 and https://github.com/kubeflow/testing/tree/master/apps-cd * This is the old code for updating the jupyter web app and is no longer needed.
* Events are cluster scoped resources. Users are only granted access to specific namespaces though. * So we can't do a subject access review check for events.
* add license info and content * update Dockerfile
* fix: install python3-setuptools and python3-pip * fix: add `python3-dev` * fix: symlink bug * Install AWS CLI in the Dockerfile * Add support for tensorflow 1.15 jupyter images * Add new jupyter notebook images
) * Pushed license_info.csv file, 1287 entries (19 failures -> manually added) * Moved file to a more appr location * License updates done, with manual research against github * Generated license.txt and tackled @zhenghuiwang's comments
…eflow#4717) * Update the documentation for how to publish/release the website. * The big change is that we instead of creating new Netlify sites for each version of the website we will take advantage of Netlify's ability to automatically deploy branches. * Using branch deploys has two many advantages 1. Managing multiple Netlify sites is an administrative challenge. * In particular, when the new site is created the creator needs to ensure they create it under the kubeflow-team otherwise it will be private to them. * This has not been happening. Only the v0.5 and www.kubeflow.org sites are currently under the kubeflow-team in Netlify. * We have no easy way to track down the owner of the individual sites or gain access if they are unavailable 2. Using branch deploys should be much simpler than setting up a new Netlify site. * In addition we can take advantage of Netlify to use a different branch from master for the production website (i.e. www.kubeflow.org) * This allows us to start preparing the docs on master for an upcoming release while still showing stable docs corresponding to the current release to users. * Using the branch deploy feature the docs on master should be available at htts://master.kubeflow.org. Related to kubeflow/website#1581 * Address comments. * address comments. * Address comments.
* Delete dead code for releasing and updating images.
* These scripts were a much earlier attempt to try to manage image tags
as part of releases.
* These scripts were abandoned several releases ago.
* We have new infrastructure
see: https://github.com/kubeflow/testing/tree/master/apps-cd
to make it easier to consistently apply semantic tags e.g "vx.y.z"
to images and update the kustomize manifests
* We should no longer need to worry about dealing with tags being moved
because the plan is to use tags + image shas see: kubeflow/testing#558
* update_components.sh is obsolete since we no longer use ksonnet.
* Remove the obsolete releaser for the jupyter-web-app.
* Remove the entries for the releaser jobs from the prow config.
* Added website url to IAP * fix typo
* Updates to install Fairing from PyPI * Updated to pin kubeflow-fairing to 0.7.1
This commit fixes the event filtering check, so it doesn't crash when
the Pod name doesn't contain a dash ("-").
Signed-off-by: Yannis Zarkadas <yanniszark@arrikto.com>
…od (kubeflow#4713) (kubeflow#4782) * Allowing for an env var ADD_FSGROUP to be set to false to suppress the automatic addition of fsGroup: 100 in the pod's security context. This addresses issue kubeflow#4617. * Adding note in README regarding ADD_FSGROUP.
…beflow#4751) * Add AWS IAM Role for ServiceAccount support in profile controller * Add eks profile iam plugin instructions and examples * Clean up codes and add unit tests * Optimize character size of policy document * Always set oidc audience to trust identity * Support AssumeRoleWithWebIdentity call via
* End-to-end testing added: - Error surfacing - HTML mismatch verification - User dirty state verification - Registration flow logic (thanks to @prodonjs) - Comments explaining all ENV values, and where to get them from, including docs - Small fix in API_Workgroup (type related - non functional) - Tabbed output * Make sure to mandate that all env args are actually passed in! * Allow users to nuke their own profile programatically * Test cleanup logic + cleanup help logs added! * Docs added, nits: - Docs updated to reflect all open questions, stack choices, running instructions, and methodology - Fixed nits from @kimwnasptd
* Now using distroless latest for admission-webhook Dockerfile * using base-debian10 * using static * using static-debian10 with tag. latest is not available yet
…#4791) * Remove dead tests and notebook image release on postsubmit. * We no longer want to run building and publishing of tensorflow notebook images on postsubmit because we won't have permission in the CI infrastructure to push to gcr.io/kubeflow-images-public. * See kubeflow#4789 for fixing Notebook image CD * The minikube tests aren't being maintained so just get rid of them * We have migrated off of ksonnet to using python workflows which are triggered off the kfctl repo. * Restore workflows.libsonnet.
…fam response. Allows proper cleaning after test (kubeflow#4869)
The jupyter-web-app component is superceded by StatCan/jupyter-apis. This commit stops building the redundant component.
Run container scanning as a step after building rather than its own job so that it can find the target image.
* Upgrades packages to fix high and critical severity vulnerabilities * Refactor to use updated Kubernetes client API
V1.2 branch pipeline fix
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolves #34