gitlabRunner update to 0.63.0-bb.10
Package Merge Request
Package Changes
https://repo1.dso.mil/big-bang/product/packages/gitlab-runner/-/blob/0.63.0-bb.7/CHANGELOG.md
Package MR
big-bang/product/packages/gitlab-runner!156 (merged) (old)
big-bang/product/packages/gitlab-runner!158 (merged) (new)
For Issue
For #1931 (closed)
For big-bang/product/packages/gitlab-runner#104 (closed)
Upgrade Notices
A New Package Value for Gitlab Runner has been added ".Values.networkPolicies.kubeapiPort". This is currently implemented in the network policy for Gitlab Runner to allow explicit Kube API access in conjunction with ".Values.networkPolicies.controlPlaneCidr".
Defaults for values above if not set:
".Values.networkPolicies.controlPlaneCidr" default value is "0.0.0.0/0"
".Values.networkPolicies.kubeapiPort" default value is ("443", "6443")
Merge request reports
Activity
- A deleted user
added botmr gitlabRunner statusreview labels
assigned to @matt.vasquez
requested review from @chris.oconnell and @michaelmartin
changed milestone to %2.27.0
added 5 commits
-
c73c394c...cb9071f2 - 4 commits from branch
master
- f5b35805 - Merge branch 'master' into 'update-gitlab-runner-tag-0.63.0-bb.7'
-
c73c394c...cb9071f2 - 4 commits from branch
requested review from @ryan.thompson.44
@andrewshoell : You have been tagged in this merge request for the purpose of conducting secondary review.
changed milestone to %2.28.0
@chris.oconnell so that is handled by the if statement in the package kubeapi network policy helm template. Basically if kubeapiPort is NOT set, ports 443 and 6443 are defined in the network policy, hence "default".
- Resolved by Christopher O'Connell