static host based routing lab -- Producer app uses "operator" namespace instead of "confluent"
chuck-confluent opened this issue · comments
the producer app yaml file uses "operator" rather than "confluent" namespace.
@arodoni Thanks! It gives an error because that namespace is never created in this lab. I would suggest being consistent with the loadbalancer lab that creates a namespace called myclient, or perhaps even more descriptive like separate-kafka-client-namespace to underscore that the client is able to reach kafka from outside.
It does still bother me that this lab doesn't have a client from entirely outside the kubernetes cluster. We would need to create a truststore outside of kubernetes for this to work.
It looks like the producer app actually must be in the "confluent" namespace. Otherwise, it won't have access to the kafka-pkcs12 secret that is created in the confluent namespace. I am not 100% sure, but I think that secret is generated by the operator when creating confluent services.