Paul Gier
Paul Gier
I'm running into some problems due to the large size of the cluster CRD. I sometimes get memory errors in K9s/kubectl, and it can be a bit difficult to find...
I don't see an option in the spec for additionalVolumes in the bastion. Currently bastion can't connect to the proxy because it doesn't have the required tokens mounted.
To keep the generated values more concise and allow for easier review, the migration tool should only print values which override the defaults. An alternative might be a tool to...
If I manually delete the proxy configmap, the operator can get into a bad state where it's waiting for the proxy pods to come up, but they can't come up...
We have services configured with a "-local" suffix. When running the migration tool against this cluster, it fails with this error: ``` 17:09:49.469 [main] DEBUG org.jboss.logging - Logging Provider: org.jboss.logging.Slf4jLoggerProvider...
Custom proxy container args seem to be ignored by the migration tool
Currently the Pulsar pod scrape configuration is included directly in the kaap-stack Helm values. https://github.com/datastax/kaap/blob/8e2473ffa7f0719a466316fdfd35657d1f904848/helm/kaap-stack/values.yaml#L354-L385 The problem is that this cannot be used across namespaces. So if kube-prometheus-stack is installed...
Astra streaming proxy containers have defined additional volumes for mounting secrets, however, the migration tool seems to ignore these.
@michaeljmarshall can you take a look at adding this feature?
The migration tool didn't add imagePullSecrets to the generated proxy config