mammoth-postman-10874
04/12/2023, 10:23 AMmost-kite-870
04/13/2023, 8:30 AM<https://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@github.com/myorg/c-nginx.git> refs/heads/main error: exit status 128, detail: remote: Invalid username or password. fatal: Authentication failed for '<https://github.com/myorg/c-nginx.git/>'
mysterious-whale-87222
04/13/2023, 9:32 PMchart requires kubeVersion: >=1.22.0-0 which is incompatible with Kubernetes v1.20.0
but my cluster version is Server Version: <http://version.Info|version.Info>{Major:"1", Minor:"25", GitVersion:"v1.25.6", GitCommit:"ff2c119726cc1f8926fb0585c74b25921e866a28", GitTreeState:"clean", BuildDate:"2023-01-18T19:15:26Z", GoVersion:"go1.19.5", Compiler:"gc", Platform:"linux/amd64"}
What can cause this?steep-furniture-72588
04/18/2023, 7:05 AMpowerful-florist-21503
04/20/2023, 2:32 PMdefaultNamespace: monitoringfleet
kustomize:
dir: ""
helm:
chart: <https://xxxxxx.yyyyyyy.xxxxxxxxxxx.com/artifactory/api/helm/vii-helm/_external/https/cdn.zabbix.com/zabbix/integrations/kubernetes-helm/6.0/zabbix-helm-chrt-1.1.1.tgz>
releaseName: "zabbixfleet"
values:
zabbixProxy.env[1].value: ${ .ClusterName }
valuesFiles:
- zabbix_values.yaml
So Im trying to pass my cluster name (${ .ClusterName }
as a value to the helm chart. I get no error on Rancher UI and I was unable to find any relevant logs what could be the issue, but fleet does not install the chart with the clustername, it does not reconcile. I believe there is some error in that above yaml? How to pass cluster name to helm chart or pass cluster annotations to helm chart?rhythmic-night-12176
04/20/2023, 4:44 PMfleet.yaml
files. Each one of those has several corresponding GitRepo
s in Continuous Delivery each one pointing at different clusters. This lets us change a branch on a GitRepo
pointing to a sandbox cluster so we can POC changes without affecting production. Once the branch gets merged to main
branch the changes are propagated to all clusters that reference the main
branch.
This works really well but it's a huge bottleneck because only one engineer can be referencing that sandbox cluster at a time with their selected development branch.
Question: Has anyone else run into this and does anyone have any examples of ways they've solved this in the past? I can't really give everyone their own sandbox cluster yet, unfortunately, or I'd just do that.powerful-florist-21503
04/21/2023, 11:18 AMvalues:
and valuesFiles:
at the same time. For example, I have fleet.yaml:
values:
zabbixProxy:
env:
- name: "ZBX_HOSTNAME"
value: <http://global.fleet.clusterLabels.management.cattle.io/cluster-display-name|global.fleet.clusterLabels.management.cattle.io/cluster-display-name>
valuesFiles:
- zabbix_values.yaml
This is resulting that ZBX_HOSTNAME
is not passed to helm. If I disable use of that values file, then the ZBX_HOSTNAME
is passed to helm. Is this expected behaviour?billowy-apple-60989
04/21/2023, 12:34 PMhundreds-evening-84071
04/24/2023, 7:55 PMFleet User
and assigned to my user.
The user has Cluster Owner permission (to a downstream cluster)
Was able to add a git repo into Fleet, but the list of clusters is blank (in Fleet)
In Cluster Management screen the cluster is accessible.
What am I missing?hundreds-sugar-37524
04/28/2023, 4:25 PMrefined-analyst-8898
04/28/2023, 5:27 PMmillions-notebook-58367
04/29/2023, 5:49 PMprovider=gcp
defaultNamespace: kube-system
helm:
releaseName: metrics-server
chart: metrics-server
repo: <https://charts.bitnami.com/bitnami>
values:
apiService:
create: true
securePort: 4443
extraArgs:
- --cert-dir=/tmp
- --kubelet-insecure-tls=true
- --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname
targetCustomizations:
- clusterSelector:
matchLabels:
provider: gcp
helm:
disabled: true
Something like thisrefined-analyst-8898
04/30/2023, 12:31 AMrefined-analyst-8898
04/30/2023, 1:20 PMstrong-action-21448
05/02/2023, 1:33 PMChart requires kubeVersion: >=v1.24.0-0 which is incompatible with Kubernetes v1.20.0
It seems like this indicates rancher is using an old kubectl client when deploying helm charts, and I'm not sure how to upgrade fleet's kubectl?bored-australia-39597
05/02/2023, 2:45 PMbored-australia-39597
05/02/2023, 2:54 PMhundreds-evening-84071
05/03/2023, 11:08 PMhundreds-sugar-37524
05/04/2023, 10:41 AMtargetCustomizations
in fleet.yml so based on cluster name, fleet pulls from different repo.
It works only for one of my cluster, because helmSecretName
in my gitRepo
refers to the account from one of the helm registry. Can I override this in my fleet.yml or can I define multiple account in helmSecretName
?
My fleet.yml looks like this:
helm:
repo: repo-a
chart: my-chart
targetCustomizations:
- name: cluster-b
clusterName: cluster-b
helm:
repo: repo-b
chart: my-chart
ambitious-plastic-3551
05/07/2023, 4:28 PMambitious-plastic-3551
05/07/2023, 4:34 PMambitious-plastic-3551
05/07/2023, 4:36 PMambitious-plastic-3551
05/07/2023, 4:38 PMambitious-plastic-3551
05/07/2023, 5:08 PMtime="2023-05-07T17:06:31Z" level=info msg="Deleting unknown bundle ID gl-konstanta-ops-k8s-sites-viaint-si-viaint-si--ff6e8, release via-international/gl-konstanta-ops-k8s-sites-viaint-si-viaint-si-ff6e8, expecting release via-international/gl-konstanta-ops-k8s-sites-viaint-si-viaint-si--ff6e8"
time="2023-05-07T17:06:31Z" level=info msg="uninstall: Deleting gl-konstanta-ops-k8s-sites-viaint-si-viaint-si-ff6e8"
ambitious-plastic-3551
05/07/2023, 5:08 PMambitious-plastic-3551
05/07/2023, 5:09 PMambitious-plastic-3551
05/07/2023, 5:40 PMbillowy-apple-60989
05/08/2023, 12:33 PMGitRepos
in Fleet that deploy some apps and cluster-config to 35+ downstream clusters, these repos all watch master/main branches.
Now if i want to make a change to one of these deployed apps (update, config change, whatever else) i'd like to try this out on a few clusters before pushing it to all clusters, how would i do this? Create a new GitRepo
that watches a new branch and only deploys to specific clusters? Some other way?
Thankshundreds-evening-84071
05/08/2023, 6:03 PMfreezing-holiday-13112
05/09/2023, 10:43 PM