Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multi-distro support #153

Closed
wants to merge 18 commits into from
Closed

Conversation

jeff-mccoy
Copy link
Contributor

@jeff-mccoy jeff-mccoy commented Nov 3, 2021

Multi-distro support

  • add ARM support
  • adds in-memory embedded registry to serve registry image from "seed" config spec
  • handles helm charts install/upgrade/rollback/uninstall via helm directly
  • dynamically generate helm charts for raw manifests
  • add tunnel capability to access zarf endpoints without ingress config
  • flattens image collection to single tarball
  • remove root / linux requirements for zarf deployments
  • add K8s distro-detection and distro-specific seed image behaviors
  • document local registry per https://github.com/kubernetes/enhancements/tree/master/keps/sig-cluster-lifecycle/generic/1755-communicating-a-local-registry
  • reorganize logging, remove logrus, replace with pterm, add progress cli feedback
  • add support for stacking helm values files
  • normalize log levels: info, warn, debug, trace
  • update go mod deps
  • move zarf state to a k8s secret in the zarf namespace
  • support zarf destroy for 3rd-party clusters
  • move crane image cache to sub folder under home
  • add support for multiple users with htpasswd
  • add path key for git-based helm charts
  • remove need for PKI prompts on default init
  • add storage class tracking in zarf state for multi-distro compatibility

@jeff-mccoy jeff-mccoy force-pushed the native-apply-with-argo-gitops-engine branch 2 times, most recently from df0a0fa to 5986b69 Compare November 6, 2021 07:22
cli/internal/helm/charts.go Outdated Show resolved Hide resolved
cli/internal/helm/charts.go Show resolved Hide resolved
assets/manifests/registry/ingress.yaml Outdated Show resolved Hide resolved
cli/.vscode/launch.json Outdated Show resolved Hide resolved
cli/internal/packager/create.go Outdated Show resolved Hide resolved
cli/internal/k8s/gitops.go Outdated Show resolved Hide resolved
cli/internal/k8s/gitops.go Outdated Show resolved Hide resolved
cli/internal/utils/exec.go Outdated Show resolved Hide resolved
cli/internal/packager/deploy.go Outdated Show resolved Hide resolved
cli/internal/packager/deploy.go Outdated Show resolved Hide resolved
@jeff-mccoy jeff-mccoy force-pushed the native-apply-with-argo-gitops-engine branch 5 times, most recently from 9510dc5 to 295dd38 Compare November 15, 2021 06:36
zarf.schema.json Outdated Show resolved Hide resolved
zarf.yaml Outdated Show resolved Hide resolved
@jeff-mccoy jeff-mccoy force-pushed the native-apply-with-argo-gitops-engine branch from e33282f to 2f62f21 Compare November 30, 2021 02:18
@jeff-mccoy jeff-mccoy force-pushed the native-apply-with-argo-gitops-engine branch from a2e8c30 to 351cc6a Compare December 2, 2021 23:21
cli/config/config.go Outdated Show resolved Hide resolved
@jeff-mccoy jeff-mccoy force-pushed the native-apply-with-argo-gitops-engine branch 2 times, most recently from f121310 to 38c1b93 Compare December 11, 2021 07:09
@jeff-mccoy jeff-mccoy force-pushed the native-apply-with-argo-gitops-engine branch from 260c4bc to 2c768e1 Compare December 28, 2021 01:20
cli/cmd/destroy.go Show resolved Hide resolved
cli/config/config.go Outdated Show resolved Hide resolved
cli/cmd/connect.go Outdated Show resolved Hide resolved
cli/cmd/connect.go Show resolved Hide resolved
cli/internal/packager/seed.go Outdated Show resolved Hide resolved
cli/cmd/connect.go Outdated Show resolved Hide resolved
cli/cmd/connect.go Outdated Show resolved Hide resolved
@YrrepNoj

This comment has been minimized.

@jeff-mccoy jeff-mccoy force-pushed the native-apply-with-argo-gitops-engine branch from 664a1f7 to 513ac4e Compare January 14, 2022 20:24
- adds in-memory embedded registry to serve registry image from "seed" config spec
- handles helm charts install/upgrade/rollback/uninstall via helm directly
- add tunnel capability to access zarf endpoints without ingress config
- flattens image collection to single tarball
- remove root / linux requirements for zarf deployments
- add K8s distro-detection and distro-specific seed image behaviors
- document local registry per https://github.com/kubernetes/enhancements/tree/master/keps/sig-cluster-lifecycle/generic/1755-communicating-a-local-registry
- reorganize logging, remove logrus, replace with pterm, add progress cli feedback
- add support for stacking helm values files
- normalize log levels: info, warn, debug, trace 
- update go mod deps
- enable full support for helm template -> argo or helm install directly
- move zarf state to a k8s secret in the zarf namespace
- support zarf destroy for 3rd-party clusters
- move crane image cache to sub folder under home
- add support for multiple users with htpasswd
- add path key for git-based helm charts
- remove need for PKI prompts on default init
- add storage class tracking in zarf state for multi-distro compatibility
@jeff-mccoy jeff-mccoy force-pushed the native-apply-with-argo-gitops-engine branch from 513ac4e to d664647 Compare January 15, 2022 00:42
- remove registry / registry files for init package create
- only use registry on deploy if injection not available
- default to injection for k3s
- make seed registry r/w on localhost and then read-only on given host/ip
- enable proper registry teardown when done
- cleanup seed code
@jeff-mccoy jeff-mccoy force-pushed the native-apply-with-argo-gitops-engine branch from 663b07c to 0266a85 Compare January 16, 2022 09:25
@jeff-mccoy jeff-mccoy changed the title Native apply with argo gitops engine Multi-distro support Jan 19, 2022
This needs some more work to get it right, but should ease the pain around multi-arch since crane doesn't support for this.
@RothAndrew
Copy link
Contributor

Closed in favor of #237, which is the successor to this PR with a more apt branch name.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants