https://learn.acloud.guru/course/7174b900-cf14-45e9-8f42-52f153e00857/learn/246dc306-063a-4ccd-ba1c-459b768871ed/6e449fcc-e9aa-4be7-8ca5-b656cb0cc473/watch
todo courses:
https://learn.acloud.guru/course/github-actions-deep-dive/overview
https://learn.acloud.guru/course/deployment-pipelines-using-github-actions/dashboard
github: marxid/content-gitops (-forked from-) linuxacademy/content-gitops
docker image: linuxacademycontent/gitops
--
flux installation:
--
export GHUSER=marxjd
kubectl create ns flux
fluxctl install \
> --git-user=${GHUSER}
> --git-email=${GHUSER}@users.noreply.github.com \
> --git-url=git@github.com:${GHUSER}/content-gitops \
> --git-path=namespaces,qa \
> --namespace=flux | kubectl apply -f -
#qa is the monitoring folder.
you could test with workloads folder in the content-gitops repo forked
export FLUX_FORWARD_NAMESPACE=flux
env | grep GH
fluxctl identity --->grab this rsa key
github repo-->settings --> deply keys --> qa=<key copied>
wach target destination say(qa) will look in their sub folders(qa).
fluxctl sync
fluxctl list-workloads --all-namespaces
--
installation:
docs.fluxcd.io/en/stable/references/daemon.html
----
kubectl -n flux rollout status deployment/flux
fluxctl identity --k8s-fwd-ns flux
#after copying the above access key to the the github repo deploy keys section, we can run below sync command
fluxctl sync --k8s-fwd-ns flux
No comments:
Post a Comment