Update kubectl apply command in Flux install documentation
Package Merge Request
Package Changes
(Describe Package changes here)
Package MR
(Link to Package MR here)
#1775 (closed)
For IssueCloses (link to issue here)
Merge request reports
Activity
added kinddocs priority7 statusreview labels
requested review from @michaelmartin, @ryan.j.garcia, and @chris.oconnell
assigned to @montgomery.marcus
- Resolved by Ryan Garcia
I'm not sure about this one. The 'kubectl apply -k base/flux/' command I added does seem to work and install flux, but afterward the 'helm update' I normally use to deploy BB:
helm upgrade -i bigbang ./chart -n bigbang --create-namespace -f ./docs/assets/configs/example/policy-overrides-k3d.yaml -f ../overrides/registry-values.yaml -f ./chart/ingress-certs.yaml Gets me this:
NAMESPACE NAME READY STATUS RESTARTS AGE kube-system local-path-provisioner-76d776f6f9-jdtgf 1/1 Running 0 36m kube-system coredns-59b4f5bbd5-f8gsf 1/1 Running 0 36m flux-system source-controller-799f4f8dc-6rjff 0/1 ImagePullBackOff 0 24m flux-system kustomize-controller-85856876bf-fr7sn 0/1 ImagePullBackOff 0 24m flux-system helm-controller-79b777fd6c-jdh92 0/1 ImagePullBackOff 0 24m flux-system notification-controller-79dddd7fc-5dggd 0/1 ImagePullBackOff 0 24m
I'm guessing there's more configuration you'd need to do before deploying BB if you don't want to use scripts/install_flux.sh
requested review from @ryan.thompson.44 and @aperkins
@andrewshoell @rgsjustins : You have been tagged in this merge request for the purpose of conducting secondary review.
changed milestone to %2.15.0
mentioned in commit ddc164b6