-
Notifications
You must be signed in to change notification settings - Fork 339
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(k8s) Use a single scheme for all of k8s #2796
Conversation
Related to #2764 |
4ee6a30
to
ecba9f2
Compare
Codecov Report
@@ Coverage Diff @@
## master #2796 +/- ##
==========================================
+ Coverage 52.00% 52.09% +0.08%
==========================================
Files 881 882 +1
Lines 51341 51320 -21
==========================================
+ Hits 26700 26734 +34
+ Misses 22525 22460 -65
- Partials 2116 2126 +10
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice.
abb924e
to
00ba8c6
Compare
@Mergifyio update |
Command
|
We were modifying the same scheme in many places when configuring the controllers. This is unecessary and is likely to introduce bugs. We now use the same scheme for everything and modify it at initialization Signed-off-by: Charly Molter <charly.molter@konghq.com>
Co-authored-by: James Peach <jpeach@apache.org> Signed-off-by: Charly Molter <charly.molter@konghq.com>
3f8f469
to
5b4733d
Compare
* chore(k8s) Use a single scheme for all of k8s We were modifying the same scheme in many places when configuring the controllers. This is unecessary and is likely to introduce bugs. We now use the same scheme for everything and modify it at initialization Signed-off-by: Charly Molter <charly.molter@konghq.com> (cherry picked from commit fdc5f1a)
We were modifying the same scheme in many places when configuring the controllers. This is unecessary and is likely to introduce bugs. We now use the same scheme for everything and modify it at initialization Signed-off-by: Charly Molter <charly.molter@konghq.com> (cherry picked from commit fdc5f1a) Co-authored-by: Charly Molter <charly.molter@konghq.com>
* chore(k8s) Use a single scheme for all of k8s We were modifying the same scheme in many places when configuring the controllers. This is unecessary and is likely to introduce bugs. We now use the same scheme for everything and modify it at initialization Signed-off-by: Charly Molter <charly.molter@konghq.com>
* chore(k8s) Use a single scheme for all of k8s We were modifying the same scheme in many places when configuring the controllers. This is unecessary and is likely to introduce bugs. We now use the same scheme for everything and modify it at initialization Signed-off-by: Charly Molter <charly.molter@konghq.com>
Summary
We were modifying the same scheme in many places when configuring the
controllers. This is unecessary and is likely to introduce bugs.
We now use the same scheme for everything and modify it at initialization
Documentation
Testing
Backwards compatibility
backport-to-stable
label if the code is backwards compatible. Otherwise, list breaking changes.