Moved the excluded namespaces to the new regex method for excluded resources.
Merge Request
No package changes. Scope is in Big Bang only.
Excluded namespaces converted to excluded resources where the exclusion could be narrowed down to namespace and pod/container name using regex.
Values added to k3d-dev-values.yaml and ci/k3d/values.yaml to accommodate load balancer pod/container exceptions.
Additional Details
For testing, all packages should be deployed and no denies should occur. Use kubectl get events -n <namespace>
to check for denies.
closes #693 (closed)
closes #776 (closed)
Merge request reports
Activity
added 1 commit
- d9d96cb0 - Updated the documentation for the k3d developer instances
added statusreview label
- Automatically resolved by Eric Goode
- Automatically resolved by Eric Goode
- Automatically resolved by Michael McLeroy
- Automatically resolved by Michael McLeroy
- Automatically resolved by Michael McLeroy
- Resolved by Micah Nagel
- Automatically resolved by Eric Goode
- Automatically resolved by Michael McLeroy
- Automatically resolved by Michael McLeroy
- Automatically resolved by Michael McLeroy
- Automatically resolved by Michael McLeroy
- Automatically resolved by Michael McLeroy
- Automatically resolved by Michael McLeroy
- Automatically resolved by Michael McLeroy
- Automatically resolved by Michael McLeroy
- Automatically resolved by Michael McLeroy
@egoode a lot of comments but they all boil down to the same couple of things:
- make sure our conditionals are on the proper packages (mostly fluentbit, these were pre-existing issues but we should clean them up while we're modifying these values)
- make sure that we're using the
excludedResources
as intended: the goal is to restrict our exceptions down further than just the namespace. As is, most of these just add a whole namespace exception in a different way.
What I'd suggest doing to get the pieces:
- remove the exceptions
- deploy the offending packages
- view the errors that happen (typically a describe on the deployments/daemonsets)
- the errors will output something like "gatekeeper denied this-resource-name" or "gatekeeper denied this-resource-name-xhyd"
- use that name as the
excludedResources
, sometimes we can do an exact match and sometimes we need regex due to the random strings.
removed statusreview label
added 71 commits
-
d9d96cb0...d494da88 - 70 commits from branch
master
- 722f26c5 - Merging in new changes from master
-
d9d96cb0...d494da88 - 70 commits from branch
added 53 commits
-
722f26c5...b0512faa - 52 commits from branch
master
- 17952abb - Merge branch 'master' into opa-add-regexp
-
722f26c5...b0512faa - 52 commits from branch
added 28 commits
-
ac191ab8...66272e52 - 27 commits from branch
master
- ccf0cf55 - Merge branch 'master' into opa-add-regexp
-
ac191ab8...66272e52 - 27 commits from branch
added 1 commit
- 27d633fc - fix(gatekeeper): fluentbit conditional updated
added statusreview label
added 3 commits
-
7859b52e...a8a66f3e - 2 commits from branch
master
- 36d16708 - Merge branch 'master' into opa-add-regexp
-
7859b52e...a8a66f3e - 2 commits from branch
enabled an automatic merge when the pipeline for 36d16708 succeeds
mentioned in commit e3eb8bbf