Open atropos112 opened 11 months ago
Thank you so much for this issue, I was affected by exactly those issues and was scratching my head for a while
Thanks a lot for the details. You saved me a lot of time! This needs to be fixed urgently!
Here we use Flux2 and reconciliation failed because of :
securityContext:
...
fsGroup: 1000
This "field" does not exist in the API. After removing it from our kustomization, everything fell into place.
Which document needs to be updated? https://ot-redis-operator.netlify.app/docs/getting-started/cluster/
Expected changes Current yaml example there is
apiVersion: redis.redis.opstreelabs.in/v1beta1
is outdated and will fail withunless you are running in the same namespace as where the operator is (which often is not the case surely)
If you update to
apiVersion: redis.redis.opstreelabs.in/v1beta1
toapiVersion: redis.redis.opstreelabs.in/v1beta2
one also needs to adjustsecurityContext
topodSecurityContext
as otherwise you will getIt would be much appreciated to outline that v7.0.5 or v7.0.12 will not work with ARM64 devices (entrypoint.sh can't be exec'd by this arch) and if the individual is to have hope here they should use latest tag.
What version of redis-operator are you using?
redis-operator version: 0.15.9
Additional context I would appreciate re-deployment of the latest tag of
quay.io/opstree/redis
with a version tag to allow people with arm64 devices to not have to stick with the ever changing latest tag. I realise this is not this repo's issue, I can raise it there if needs be.