[dev-v2.8] rancher-logging 103.1.0+up4.4.0 update #3787
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Validation steps
Ex:-
longhorn-controller:
repository: rancher/hardened-sriov-cni
tag: v2.6.3-build20230913
|
HarrisonWAffel
force-pushed
the
2.8-windows-logging-version
branch
from
d438862
to
db32b53
Compare
Validation steps
Ex:-
longhorn-controller:
repository: rancher/hardened-sriov-cni
tag: v2.6.3-build20230913
|
HarrisonWAffel
force-pushed
the
2.8-windows-logging-version
branch
from
db32b53
to
6b33385
Compare
Validation steps
Ex:-
longhorn-controller:
repository: rancher/hardened-sriov-cni
tag: v2.6.3-build20230913
|
joshmeranda
requested changes
Apr 18, 2024
HarrisonWAffel
force-pushed
the
2.8-windows-logging-version
branch
from
6b33385
to
adb8f9c
Compare
Validation steps
Ex:-
longhorn-controller:
repository: rancher/hardened-sriov-cni
tag: v2.6.3-build20230913
|
joshmeranda
approved these changes
Apr 18, 2024
HarrisonWAffel
force-pushed
the
2.8-windows-logging-version
branch
from
adb8f9c
to
f44a07e
Compare
Validation steps
Ex:-
longhorn-controller:
repository: rancher/hardened-sriov-cni
tag: v2.6.3-build20230913
|
lucasmlp
requested changes
Apr 18, 2024
regsync.yaml
Outdated
There was a problem hiding this comment.
This file should not be changed by contributors. We have a GitHub action that automatically detects new docker images and updates regsync.yaml
There was a problem hiding this comment.
I've removed the changes to regsync.yaml.
HarrisonWAffel
force-pushed
the
2.8-windows-logging-version
branch
from
f44a07e
to
36f012d
Compare
Validation steps
Ex:-
longhorn-controller:
repository: rancher/hardened-sriov-cni
tag: v2.6.3-build20230913
|
lucasmlp
changed the title
lucasmlp
pushed a commit
that referenced
this pull request
Apr 25, 2024
6 tasks
lucasmlp
pushed a commit
that referenced
this pull request
Apr 25, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue: rancher/windows#222
Problem
Various components of Rancher are using Windows images which contain Foreign Layer references. This makes mirroring these images more difficult and is a common source of user confusion when configuring windows nodes in air-gapped environments. Other PRs to rancher/rancher and rancher-monitoring have already resulted in many of these images being fixed, however logging has not yet been addressed.
Solution
v1.8.10v1.8.10is simply a rebuilt version of1.8.9which no longer contains foreign layer references. There is no functional difference between the two.rancher-logging 103.1.0-rc1+up4.4.0rancher-logging 103.1.0-rc2+up4.4.0Testing
I've confirmed the chart can be installed and works as expected. I've confirmed that
v1.8.10of rancher/fluent-bit does not include any foreign layer references.Engineering Testing
Manual Testing
Automated Testing
QA Testing Considerations
Regressions Considerations
Backporting considerations