Regarding configmap

[afzal442]

I tinkered with the code I wondered why you have created configmap. Can we call it without configmap? Thanks.

e.g.

client-go-examples/informer-typed-simple/main.go

Line 118 in fe6ecf3

cm := &corev1.ConfigMap{Data: map[string]string{"foo": "bar"}}

cc: @iximiuz

[iximiuz]

Hi Afzal! I use ConfigMaps there as a simple Kubernetes Object example. I could have chosen any other type of Kubernetes Objects (Deployments, Pods, etc.). I.e., no ConfigMaps is needed to make informers work. But w/o created/deleting objects the informer example would be incomplete.

[afzalbin64]

Hmm, makes sense now. I understood the reason behind the use of ConfigMaps obj. If we use any other K8s obj like Pods, Deployment etc., then I think we don't have to write other methods like creating/deleting objects. Isn't that correct? thanks.

[iximiuz]

I'm not sure if I understood your clarification fully. What exactly methods are you referring to?

[afzal442]

Sorry for that confusion. I mean that as we write methods for creating/deleting configmap object, we don't have to write methods when we consider other obj such as Pods, Deployments etc. Does that make sense? Thanks.

[iximiuz]

Since this is an example of a typed informer, I don't think you can reuse it for other types of resources such as Pods or Deployments. But the code for these types of resources will be very similar.

[afzal442]

Thanks Ivan, got that. Another general confusion is whether we need to write methods for other resources like Pods etc. if we try to take an example of Pod object instead. e.g. func createPod and func deletePod as an use case of informer(). 🏷️