Skip to content

feat: Add multi-arch add-clusters image #104

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

Open
wants to merge 33 commits into
base: main
Choose a base branch
from

Conversation

dacamposol
Copy link

@dacamposol dacamposol commented Nov 2, 2022

Context

In the original image, bitnami/kubectl is being used as base, which only exists in the Docker Registry in amd64 architecture as the kubectl binary is only available in that architecture.

Currently, and since Kubernetes 1.24; it's normal to find more and more ARM-based Kubernetes nodes, and the current add-cluster script won't work to set up these (the spawned Pod from the Job will fail stating the mismatch between architectures), provoking a sense of cumbersome setup to the cluster administrator. This caveats have an easy solution, as the Kubernetes CLI has been already provided in arm64 version for a while.

Solution

Since I faced the previously mentioned problems on the setup of my cluster in CodeFresh, I created a custom image which uses the script defined in this repo (add-cluster.sh) but using bitnami/minideb as base (available in both amd64 and arm64 architectures).

That image is the one that I'm proposing to include in the official repository.

Why the PR?

In order to use custom images, I required to run the cf cluster add codefresh-hosted --dry-run command and to manually modify the image used in the Job.

I think that offering an official multi-arch image would be better and would improve the onboarding process for those who have Kubernetes Clusters with ARM nodes.

PS: Additionally, the proposed Dockerfile has less vulnerabilities than the official image by bitnami/kubectl, having this one only low severity vulnerabilities while the bitnami/kubectl one has some high and medium severity vulnerabilities.

Signed-off-by: Daniel Campos Olivares <[email protected]>
dacamposol and others added 20 commits November 2, 2022 11:57
* Up version

* Up version

* Up proxy version

* Wip

* Back version

* Wip
* add applications to app-proxy rbac

* bump

* remove version bump
* add initContainer to app-proxy
* fix appset

* fix hosted installation

* fix hybrid install

* argocd 2.4 install

* Debug

* Revert "Debug"

This reverts commit c02c9af.

Co-authored-by: danielm-codefresh <[email protected]>
* Revert "move hosted to 2.4 (codefresh-io#129)"

This reverts commit 22f5ef5.

* Revert "fix appset (codefresh-io#133)"

This reverts commit aeeeb3a.

* fix
* update app-proxy

* hybrid test

* Revert "hybrid test"

This reverts commit e656ba8.
* Release 0.1.16 (codefresh-io#134)

releasing 0.1.16

* Revert "Revert hosted move to argocd 2.4 (codefresh-io#139)"

This reverts commit b63acd3

* hosted 2.4

* hosted 2.4

* runtime.yaml

* fix hybrid

* fix hybrid

* revert VERSION

Co-authored-by: Daniel Maizel <[email protected]>
* =upgrade argo-workflows

* fix changed ns

* wip

* wip

* wip

* wip

* wip

* wip

* wip

* wip

* wip

* wip

* prepare for merge

* wip

* prepare for merge

* update tag to 3.4.4
* mount argocd-token to app-proxy env
* bumped app-proxy to 1.2016.2

Co-authored-by: Noam Gal <[email protected]>
Co-authored-by: andrii-codefresh <[email protected]>
argo-cd version update with rollback query
danielm-codefresh and others added 12 commits December 21, 2022 16:42
* Revert "Revert "upgrade argo-workflows to 3.4 (codefresh-io#144)""
* add namespace override for argo-workflows

Co-authored-by: danielm-codefresh <[email protected]>
…defresh-io#158)

* automatically merge release branch to main

* add component version to release notes
* bump app-proxy

* bump

* trigger

* trigger

* bump

* remove redundent bump
change back to argocd user/password instead of token
…defresh-io#163)

* readme

* add permissions for app-proxy to read, list and patch deployments
* new rollouts version

* update rollouts
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.

9 participants