build(manifests): quick-start
should use cluster-install
#12557
Merged
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.
Follow-ups to #12445 and this related Slack thread
Motivation
prior to docs: change quick-start guide to use quick-start install. Fixes #12391 #12445, the quick start docs used the
install.yaml
instead of thequick-start-minimal.yaml
manifestsinstall.yaml
is a cluster install, soquick-start-minimal.yaml
should also use a cluster install to match the past behaviorwithout the
cluster-install
, you have to manually navigate to theargo
namespace in the UIthe quick start manifests already have fairly broad permissions (in order to get started quickly) and several warnings about not using them in prod, so this usage would be consistent
Modifications
use
cluster-install
instead ofnamespace-install
in the quick start manifests--namespaced
should not be used anymore now that we use a cluster install--auth-mode=server
codegen
manifests/quick-start*.yaml
add
manifests/**
tocodegen
on CI'schanged-files
checkVerification