George Gaál

/remove-lifecycle stale

Logs are attached ``` {"level":"info","ts":"2024-01-31T11:07:01.629Z","logger":"setup","msg":"initializing service controller","aws.service":"ec2"} {"level":"info","ts":"2024-01-31T11:07:02.696Z","msg":"Waited for 1.042559256s due to client-side throttling, not priority and fairness, request: GET:https://172.20.0.1:443/apis/snapshot.storage.k8s.io/v1\n"} {"level":"info","ts":"2024-01-31T11:07:07.860Z","logger":"setup","msg":"starting manager","aws.service":"ec2"} {"level":"info","ts":"2024-01-31T11:07:07.860Z","logger":"controller-runtime.metrics","msg":"Starting metrics server"} {"level":"info","ts":"2024-01-31T11:07:07.860Z","msg":"attempting to acquire leader lease...

Fixed by changing `HelmRelease` description according to FluxCD documentation https://fluxcd.io/flux/components/helm/helmreleases/#controlling-the-lifecycle-of-custom-resource-definitions ``` apiVersion: helm.toolkit.fluxcd.io/v2beta1 kind: HelmRelease metadata: name: ack-ec2-controller namespace: ack-system spec: install: crds: CreateReplace # HERE remediation: retries: 3 upgrade:...

@a-hilaly Hi! Just two observations 1. should EC2 controller fail if there is no corresponding CRDs? Probably no, as known resources should be managed properly. 2. Helm has a very...

The same with controllers: eks-controller @1.2.1 iam-controller @1.3.3 lambda-controller @1.3.6 route53-controller - the same effect...

@a-hilaly Hi! I am kindly asking also add tags for eks/iam/lambda/route53 controllers, as all of them are affected. Regarding your question - it is error about missing CRDs **leading to**...

@a-hilaly yes, I have already **fixed** the issue - https://github.com/aws-controllers-k8s/community/issues/2007#issuecomment-1918914506 Otherwise (in environment without FluxCD/Argo) I would just remove helm manually and install it back (and it is really interesting...

/remove-lifecycle stale

/remove-lifecycle stale

@RedbackThomson Hi! More details: I did not changed both fields in the S3 object definition.