README Flux install points to an missing YAML file

In the deployment steps https://repo1.dso.mil/platform-one/big-bang/customers/template#deploy

When deploying flux this command is used curl https://repo1.dso.mil/platform-one/big-bang/bigbang/-/raw/master/scripts/deploy/flux.yaml | kubectl apply -f -

However that URL is no longer valid, it results in a 404, and over in the big-bang/bigbang repo I can see no equivalent file

Are these steps out of date?

changed the description

added flux label

changed milestone to %1.12.0

changed iteration to Big Bang Iterations Jun 29, 2021 - Jul 12, 2021

Thanks for opening this issue! You are correct the docs are out of date, we switched to a kustomize way of deploying flux.

We typically recommend folks use the script here to install.

The most 1:1 with how we instruct folks to do it here is kustomize build "$FLUX_KUSTOMIZATION" | kubectl apply -f - where FLUX_KUSTOMIZATION=base/flux in the BigBang repo (this folder). Hope that helps in the interim until we can fix this in the docs.

I'll prioritize this for our next sprint.

To BB folks: due to the way the customer template works (no branches allowed), you will have to work off a fork and/or push direct to master. Ping me if you need help with this.

set weight to 1

added priority6 label

added kinddocs label

Hey thanks for the speedy reply! Glad I wasn't being dumb! Just taking a look at getting BigBang deployed on Azure and wrapping my head around everything right now, I'm trying that install_flux script now.

I figured with the way Flux works it's going to need to be out of a fork of the repo. Is it safe to push to public GitHub as my origin? I don't think I can fork here in GtiLab, and I've not worked with sops before so I'm not sure how safe having those secrets there in the repo is

Yep so as long as you keep your private SOPS/GPG key local and don't push it, it's safe to do this. The only way to decrypt those files is by having that private key, provided you always make sure to only push encrypted files

added Good First Issue label

assigned to @mark.sanchez

added statusdoing label

added statusblocked label and removed statusdoing label

Awaiting for account modification that will allow me to fork customer template repo.

Working currently.

added statusdoing label and removed statusblocked label

mentioned in merge request !3 (merged)

Update Readme instruction for flux deployment using kustomize build "$FLUX_KUSTOMIZATION" | kubectl apply -f -

merge request ready for review

added statusreview label and removed statusdoing label

added statusdoing label and removed statusreview label

mentioned in commit ea20cb16

closed with merge request !3 (merged)

removed statusdoing label