We’ve tried to install hybrid Apigee on bare metal using the helm charts v1.16.1-hotfix1 and keep getting errors on the apigee-datastore helm chart relating to annotations being null. Should we be using the overrides.yaml file to populate cassandra.annotations with something or are the annotations used for further installation?
Same thing with 1.15.1 except failure is on telemetry this time same issue though annotations are null:
Error: release telemetry failed, and has been uninstalled due to rollback-on-failure being set: ApigeeTelemetry.apigee.cloud.google.com “apigee-telemetry” is invalid: [spec.components.collector.annotations: Invalid value: “null”: spec.components.collector.annotations in body must be of type object: “null”, spec.components.metricsApp.annotations: Invalid value: “null”: spec.components.metricsApp.annotations in body must be of type object: “null”, spec.components.containerLogs.annotations: Invalid value: “null”: spec.components.containerLogs.annotations in body must be of type object: “null”, spec.components.metricsAdapter.annotations: Invalid value: “null”: spec.components.metricsAdapter.annotations in body must be of type object: “null”, spec.components.metricsProxy.annotations: Invalid value: “null”: spec.components.metricsProxy.annotations in body must be of type object: “null”]
Hello @Dominik_Kupczynski, welcome to the Apigee Community!
While we wait for the community to share their expertise, I encourage you to explore our Knowledge Hub, it features a collection of curated articles and videos created by Googlers.
Hi, the custom annotations are for attaching some metadata to the specified hybrid component pods and you can define them in overides see here and also config property reference for could be defined here
Quick question, do you have any 3rd party tooling that adds annotations to all pods in your cluster by default ?
Also do you see any details in logs suggesting this is happening, if it is you may want to raise a support ticket for deeper analysis on this.
Thanks Ayos we’ve already given up on this product. The setup documentation had bits missing, the setup was particularly convoluted. Also the fact that you update versions without changing the version number was frustrating especially when an updated version fixed some of the issues but still displayed the old version. Only difference was the date when it was published, that’s not usually how software versioning is done.
Thanks for the feedback, we will share it with our docs team