clean-ability-26001
10/29/2022, 12:18 PMmost-holiday-75301
10/29/2022, 6:23 PMrefined-queen-13241
10/30/2022, 7:29 AMmost-alarm-2259
10/30/2022, 10:47 AMmicroscopic-gigabyte-18402
10/30/2022, 4:02 PMhelpful-beard-54962
10/31/2022, 9:45 AMapiVersion: v1
kind: Pod
metadata:
name: shared-storage-example
spec:
volumes:
- name: shared-data
emptyDir: {}
containers:
- name: container-1
image: nginx
volumeMounts:
- name: shared-data
mountPath: /usr/share/nginx/html
- name: container-2
image: debian
volumeMounts:
- name: shared-data
mountPath: /data
command: ["/bin/sh"]
args: ["-c", "echo Hello world > /data/index.html"]
This simple configuration doesn't work in Rancher
1. Started 1 deployment with this config
2. Increased the pods in the container to 3
3. The files created in /data
are NOT shared between the 3 containers
I do not want to use persistent volume claims because I don't need them to be persistent, I just need a folder to shared data ONLY between the pods in a deployment and for that data to be destroyed when the deployment is deletedlittle-smartphone-40189
10/31/2022, 12:57 PMproud-ram-62490
10/31/2022, 3:09 PMrapid-nightfall-35050
10/31/2022, 3:42 PM[ERROR] error syncing 'fleet-default/custom-15ddd872d7da': handler unmanaged-machine: the server has asked for the client to provide credentials (get nodes <node_fqdn)), requeuing
miniature-hairdresser-1087
10/31/2022, 4:07 PMhappy-nightfall-71899
10/31/2022, 5:19 PM~/.kube # kubectl config view
I1028 18:01:07.165096 14222 versioner.go:58] invalid configuration: no configuration has been provided
apiVersion: v1
clusters:
- cluster:
certificate-authority-data: DATA+OMITTED
server:
<https://X.X.X.X:6443>
name: rancher-desktop
contexts:
- context:
cluster: rancher-desktop
user: rancher-desktop
name: rancher-desktop
current-context: ""
kind: Config
preferences: {}
users:
- name: rancher-desktop
user:
client-certificate-data: REDACTED
client-key-data: REDACTED
~/.kube #
happy-nightfall-71899
10/31/2022, 5:27 PMred-waitress-37932
10/31/2022, 5:52 PMGet <https://nexus.company.tld:8444/v2/>: x509: certificate has expired or is not yet valid
when trying to access anything with letsencrypt certs, probably because Boot2Docker was last updated before letsencrypt switched certs.bright-fireman-42144
10/31/2022, 8:09 PMbright-fireman-42144
10/31/2022, 8:09 PMbright-fireman-42144
10/31/2022, 8:21 PMsome-dream-67513
10/31/2022, 8:55 PMuser system:anonymous was granted API permissions on the EKS cluster aus-platform-core | default service account in EKS Cluster aus-platform-core was granted admin privileges by user systemserviceaccountcattle-system:rancherIs there anyway to avoid "system:anonymous" get admin privileges from rancher account?
great-oyster-72008
11/01/2022, 5:05 AMplain-cartoon-95068
11/01/2022, 9:33 AMfew-minister-97494
11/01/2022, 12:41 PMclever-analyst-23771
modern-laptop-35841
11/01/2022, 3:08 PMmodern-laptop-35841
11/01/2022, 3:08 PMwhite-crayon-39660
11/01/2022, 3:48 PMhundreds-mouse-3032
11/01/2022, 6:42 PMhundreds-mouse-3032
11/01/2022, 6:42 PMhundreds-mouse-3032
11/01/2022, 6:42 PMkind-needle-76215
11/01/2022, 7:35 PMhundreds-state-15112
11/01/2022, 8:31 PMerror syncing 'c-57xzh': handler cluster-deploy: ClusterUnavailable 503: ClusterUnavailable 503: cluster not found, requeuing
rough-carpet-50214
11/01/2022, 9:27 PMkustomize.dir
in our fleet.yaml and point to a directory with a kustomization.yaml
file in it that references a github link like this
apiVersion: <http://kustomize.config.k8s.io/v1beta1|kustomize.config.k8s.io/v1beta1>
kind: Kustomization
resources:
- <http://github.com/hashicorp/consul-api-gateway/config/crd?ref=v0.3.0|github.com/hashicorp/consul-api-gateway/config/crd?ref=v0.3.0>
The error we are getting is
Error while running post render on files: accumulating resources: accumulation err='accumulating resources from '<http://github.com/hashicorp/consul-api-gateway/config/crd?ref=v0.3.0|github.com/hashicorp/consul-api-gateway/config/crd?ref=v0.3.0>': 'crds/github.com/hashicorp/consul-api-gateway/config/crd?ref=v0.3.0' doesn't exist': no 'git' program on path: exec: "git": executable file not found in $PATH
It would appear that whatever fleet container is doing this processing does not have access to a git executable. We are working on figuring out what container this is and trying to do a custom build of it that includes git. However, I think the public image for this should include the git executable or some alternative to get this functionality working.