Graham Dumpleton

This one will actually be tricky for DaemonSet because what happens if nodes are added/removed, or the `NoSchedule` taint removed/added. Is the syncer going to be smart enough to know...

Was hoping could say: ``` --node-selector=!node-role.kubernetes.io/control-plane,!node-role.kubernetes.io/master ``` but apparently the more general Kubernetes selector format isn't allowed. I see a logged message of: ``` syncer F0914 01:30:57.619843 1 leaderelection.go:73] register...

This is proving problematic and a bit of a blocker on something we are doing. :-( The problem is that tools like `kapp` and `kapp-controller` from Carvel tools (and possibly...

As I said asking about this was theoretical as worked out whether it made sense. If it doesn't make sense you can possibly ignore it until a real need presents...

Name length is definitely a secondary issue in this case, but the primary reason it failed was that pesky ".". :-(

I actually thought you already had some strategy for long names where it would truncate them at a certain point and replace just the trailing part of the name with...

Relying on ``kubectl exec`` or ``vcluster connect`` means this action needs to be embedded in an init container or the main application container, whereas the configmap (when combined with #83...

I think in practice, due to Kubernetes community preferring Go, that an operator framework for Python is going to be a niche. So I think it is probably safe to...

So using: ``` #@ load("@ytt:data", "data") --- apiVersion: v1 kind: Namespace metadata: name: kapp-token-test #@ for n in range(data.values.count): --- apiVersion: v1 kind: ServiceAccount metadata: name: #@ "sa-{}".format(n) namespace: kapp-token-test...

A solution to this if possible would be an inbuilt rule to create secrets of type `kubernetes.io/service-account-token` after creating any service accounts, where as current behaviour seems to be to...