Adam Berlin
Adam Berlin
What's the latest on this?
Should we keep this PR as we wait for #6716 to be completed, or should we put in an issue and revisit this later?
The use-case we have is an automated workflow, as @dwsteele suggested. It would be nice to have JSON also output the annotations.
It seems that customers from different namespaces would need to be able to influence the environment of the operator to populate this env variable password, which is something I don't...
This pull request seems to be a solution to this problem: https://github.com/vmware/kube-fluentd-operator/pull/330 What can be done to move it forward?
After installing the CRD, I couldn't figure out how to make the CRDs active. I eventually pulled up the codebase and took a look around. What do you think about...
Even though the CRD gets installed by the operator once `datasource: crd` is set in the values.yaml. I think that it's an odd experience to perform a helm install and...
@javiercri That makes sense. In that case I think the default should be `.values.installCrd==true`
@javiercri I introduced the helm chart flag `installCrd` with a default of enabled. I tested these changes via `helm template` locally because I didn't see a standard way of testing...
We need to figure out what to do about the `kubectl/crd.yaml` file