Check for Namespace level config override annotations#3194
Check for Namespace level config override annotations#3194ihcsim merged 5 commits intolinkerd:masterfrom
Conversation
|
Thanks @Pothulapati, this looks and works great 👍 Could you add somewhere a test case that verifies this kind of override? Could be for example in in |
5583ad8 to
9f42ac2
Compare
|
@alpeb Added Both Unit and Integration tests :) |
|
Thanks for adding that @Pothulapati |
Signed-off-by: Tarun Pothulapati <[email protected]>
Signed-off-by: Tarun Pothulapati <[email protected]>
Signed-off-by: Tarun Pothulapati <[email protected]>
Signed-off-by: Tarun Pothulapati <[email protected]>
9f42ac2 to
62c5eab
Compare
|
Ah! I was running the test induvidually and it was working! The problem is that, the test also uses the same Changed the namespace name and it should work together with other tests. |
|
@Pothulapati Now I'm getting |
Signed-off-by: Tarun Pothulapati <[email protected]>
alpeb
left a comment
There was a problem hiding this comment.
Thanks Tarun! Integration tests are passing now for me 🥇
Followup to #3194 The namespace was too long for l5d-bot: ``` inject_test.go:117: failed to create l5d-integration-auto-git-9688d9ba-inject-namespace-override-test namespace: Namespace "l5d-integration-auto-git-9688d9ba-inject-namespace-override-test" is invalid: metadata.name: Invalid value: "l5d-integration-auto-git-9688d9ba-inject-namespace-override-test": must be no more than 63 characters ``` Signed-off-by: Alejandro Pedraza <[email protected]>
Followup to #3194 The namespace was too long for l5d-bot: ``` inject_test.go:117: failed to create l5d-integration-auto-git-9688d9ba-inject-namespace-override-test namespace: Namespace "l5d-integration-auto-git-9688d9ba-inject-namespace-override-test" is invalid: metadata.name: Invalid value: "l5d-integration-auto-git-9688d9ba-inject-namespace-override-test": must be no more than 63 characters ``` Signed-off-by: Alejandro Pedraza <[email protected]>
Fixes #2499
This PR makes the
proxy-injectorcheck for Namespace Level Override Config annotations after checking the Pod level override config annotations before going with the default values.I tried with a Cluster and it considers the annotations of the namespace before going with the defaults.
@ihcsim @grampelberg
Signed-off-by: Tarun Pothulapati [email protected]