AdheipSingh
AdheipSingh
+1 facing the same issue @robbie-demuth what are the k8s version and client version you facing this issue with ?
Here's my go mod for my operator ``` go 1.17 require ( github.com/DataDog/datadog-go v4.8.3+incompatible github.com/go-logr/logr v1.2.2 github.com/onsi/ginkgo v1.16.5 github.com/onsi/gomega v1.17.0 github.com/sirupsen/logrus v1.8.1 github.com/stretchr/testify v1.7.0 go.etcd.io/etcd/client/v3 v3.5.0 k8s.io/api v0.23.1 k8s.io/apimachinery v0.23.1...
the user should be able to just mention the nodeAffinity in the CR, templating out each and every spec in the nodeAffinity, isn't a best practice in the operator. ```...
@thenicetgp i would like to contribute too, can we collaborate ?
@seanmalloy thanks for the reply !! Here 's a code snippet which i was trying to play around with. Any practices around security context enabled, using service accounts, high quota...
@ingvagabund is this something to be taken into consideration ?
> I see a flag for watching all namespaces. I don't see why this flag is required namespace == "" should be sufficient for watching all namespaces. How about having...
yeah we still need to implement predicates for that :)
@brancz is this something we can add, would be willing to submit a PR for this
The pod spec is hardcoded with a lot of configs. Ill send out a PR to make it configurable as per user. @iampranabroy its hardcoded not customisable.