-
Notifications
You must be signed in to change notification settings - Fork 7
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
Update dependency k3d-io/k3d to v5.7.4 #133
Open
minchine
wants to merge
1
commit into
main
Choose a base branch
from
renovate/k3d-io-k3d-5.x
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
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
minchine
force-pushed
the
renovate/k3d-io-k3d-5.x
branch
5 times, most recently
from
March 27, 2023 11:32
b5dc0b6
to
1ded9a9
Compare
minchine
force-pushed
the
renovate/k3d-io-k3d-5.x
branch
8 times, most recently
from
April 7, 2023 14:31
b57abaa
to
5b014b2
Compare
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. ⚠ Warning: custom changes will be lost. |
minchine
force-pushed
the
renovate/k3d-io-k3d-5.x
branch
2 times, most recently
from
April 20, 2023 21:32
29dab2d
to
35dc8fe
Compare
minchine
force-pushed
the
renovate/k3d-io-k3d-5.x
branch
from
April 26, 2023 18:33
35dc8fe
to
4717b9e
Compare
minchine
force-pushed
the
renovate/k3d-io-k3d-5.x
branch
from
May 17, 2023 16:07
4717b9e
to
9a4e746
Compare
minchine
changed the title
Update dependency k3d-io/k3d to v5.4.9
Update dependency k3d-io/k3d to v5.5.0
May 17, 2023
minchine
force-pushed
the
renovate/k3d-io-k3d-5.x
branch
from
May 19, 2023 12:47
9a4e746
to
c38ea6e
Compare
minchine
changed the title
Update dependency k3d-io/k3d to v5.5.0
Update dependency k3d-io/k3d to v5.5.1
May 19, 2023
minchine
force-pushed
the
renovate/k3d-io-k3d-5.x
branch
from
July 5, 2023 18:09
c38ea6e
to
bc9fb64
Compare
minchine
force-pushed
the
renovate/k3d-io-k3d-5.x
branch
4 times, most recently
from
July 20, 2023 15:05
bbfc4f8
to
f2134b7
Compare
minchine
force-pushed
the
renovate/k3d-io-k3d-5.x
branch
from
July 26, 2023 19:02
c859bfb
to
ce04448
Compare
minchine
force-pushed
the
renovate/k3d-io-k3d-5.x
branch
from
August 3, 2023 05:32
ce04448
to
675ff9c
Compare
minchine
changed the title
Update dependency k3d-io/k3d to v5.5.1
Update dependency k3d-io/k3d to v5.5.2
Aug 3, 2023
minchine
force-pushed
the
renovate/k3d-io-k3d-5.x
branch
from
January 2, 2024 20:07
0887f37
to
e9f9b8b
Compare
minchine
force-pushed
the
renovate/k3d-io-k3d-5.x
branch
from
January 22, 2024 18:09
e9f9b8b
to
0d58d87
Compare
minchine
force-pushed
the
renovate/k3d-io-k3d-5.x
branch
from
April 9, 2024 17:04
0d58d87
to
1ea8f28
Compare
minchine
changed the title
Update dependency k3d-io/k3d to v5.6.0
Update dependency k3d-io/k3d to v5.6.2
Apr 9, 2024
minchine
force-pushed
the
renovate/k3d-io-k3d-5.x
branch
from
April 10, 2024 13:32
1ea8f28
to
c8676c2
Compare
minchine
changed the title
Update dependency k3d-io/k3d to v5.6.2
Update dependency k3d-io/k3d to v5.6.3
Apr 10, 2024
minchine
force-pushed
the
renovate/k3d-io-k3d-5.x
branch
from
April 17, 2024 15:07
c8676c2
to
d38c2e2
Compare
minchine
force-pushed
the
renovate/k3d-io-k3d-5.x
branch
2 times, most recently
from
May 16, 2024 12:48
f6b4af7
to
e53386b
Compare
minchine
force-pushed
the
renovate/k3d-io-k3d-5.x
branch
from
May 28, 2024 10:07
e53386b
to
e95ff63
Compare
minchine
force-pushed
the
renovate/k3d-io-k3d-5.x
branch
from
June 20, 2024 15:08
e95ff63
to
e429786
Compare
minchine
force-pushed
the
renovate/k3d-io-k3d-5.x
branch
from
July 4, 2024 12:50
e429786
to
ca4c88a
Compare
minchine
changed the title
Update dependency k3d-io/k3d to v5.6.3
Update dependency k3d-io/k3d to v5.7.0
Jul 4, 2024
minchine
force-pushed
the
renovate/k3d-io-k3d-5.x
branch
2 times, most recently
from
July 5, 2024 15:07
dcf2954
to
c45004b
Compare
minchine
changed the title
Update dependency k3d-io/k3d to v5.7.0
Update dependency k3d-io/k3d to v5.7.1
Jul 5, 2024
minchine
force-pushed
the
renovate/k3d-io-k3d-5.x
branch
from
July 15, 2024 09:09
c45004b
to
000fd19
Compare
minchine
changed the title
Update dependency k3d-io/k3d to v5.7.1
Update dependency k3d-io/k3d to v5.7.2
Jul 15, 2024
minchine
force-pushed
the
renovate/k3d-io-k3d-5.x
branch
2 times, most recently
from
July 16, 2024 15:05
c2459f9
to
3fe8b47
Compare
minchine
force-pushed
the
renovate/k3d-io-k3d-5.x
branch
from
August 2, 2024 11:32
3fe8b47
to
8f41e18
Compare
minchine
changed the title
Update dependency k3d-io/k3d to v5.7.2
Update dependency k3d-io/k3d to v5.7.3
Aug 2, 2024
minchine
force-pushed
the
renovate/k3d-io-k3d-5.x
branch
3 times, most recently
from
September 2, 2024 10:09
1b008e6
to
5e2980f
Compare
minchine
force-pushed
the
renovate/k3d-io-k3d-5.x
branch
from
September 12, 2024 10:10
5e2980f
to
5f3dfe3
Compare
minchine
changed the title
Update dependency k3d-io/k3d to v5.7.3
Update dependency k3d-io/k3d to v5.7.4
Sep 12, 2024
minchine
force-pushed
the
renovate/k3d-io-k3d-5.x
branch
from
September 13, 2024 14:08
5f3dfe3
to
6446ac7
Compare
minchine
force-pushed
the
renovate/k3d-io-k3d-5.x
branch
from
November 8, 2024 22:37
6446ac7
to
7cd9098
Compare
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.
This PR contains the following updates:
5.2.2
->5.7.4
Release Notes
k3d-io/k3d (k3d-io/k3d)
v5.7.4
Compare Source
What's Changed
New Contributors
Full Changelog: k3d-io/k3d@v5.7.3...v5.7.4
v5.7.3
Compare Source
What's Changed
Full Changelog: k3d-io/k3d@v5.7.2...v5.7.3
v5.7.2
Compare Source
What's Changed
New Contributors
Full Changelog: k3d-io/k3d@v5.7.1...v5.7.2
v5.7.1
Compare Source
Fixed
Full Changelog: k3d-io/k3d@v5.7.0...v5.7.1
v5.7.0
Compare Source
Added
Changed
Fixed
coredns-custom
configmap, so please consider this in case you're using this configmap yourself!v5.6.3
Compare Source
Changed
v5.6.2
Compare Source
Added
Changed
v5.6.0
Compare Source
Added
Changed
host.k3d.internal
and the docker runtime)Fixed
v5.5.2
Compare Source
Fixed
Invalid Host Header
issue with Docker/Moby#45935Changed
Added
v5.5.1
Compare Source
Fixed
v5.5.0
Compare Source
Added
k3d cluster create --runtime-ulimit NAME[=SOFT]:[HARD]
(same fork3d node create
)K3D_FIX_MOUNTS=1
k3d version -o json
Changed
Fixed
Deprecated
v5.4.9
Compare Source
Changed
Fixed
v5.4.8
Compare Source
Changed
Fixed
v5.4.7
Compare Source
Changed
Fixed
v5.4.6
Compare Source
Added
Changed
Fixed
v5.4.4
Compare Source
Added
Changed
sigs.k8s.io/yaml
everywhere in the project to allow for consistent json/yaml output (#1094)Fixed
k3d config init
used the legacy config format (#1091)v5.4.3
Compare Source
Added
In command
k3d registry create
k3d registry create --proxy-remote-url https://registry-1.docker.io -p 5000 -v /tmp/registry:/var/lib/registry
In config file:
...
v5.4.2
Compare Source
Added
hostAliases
in the config fileregistries.create.image
(same ask3d registry create --image
) in configv1alpha4
(no version bump) (#1056)Changed
Fixed
v5.4.1
Compare Source
Changed
v5.4.0
Compare Source
Note: This is the first independent release of k3d
Note 2: You can now fund the work on k3d using GitHub Sponsors (@iwilltry42) or IssueHunt (k3d-io/k3d)
Added
buildx
&buildx bake
for multiplatform builds (instead of VMs with the according architectures)k3d node create --k3s-arg
flag (#1032)Changed
bridge
mode for k3d-created networks for Podman compatibility (#986)Fixed
Deprecated
Removed
Compatibility
This release was automatically tested with the following setups:
Docker
Expected to Fail with the following versions:
K3s
We test a full cluster lifecycle with different K3s channels, meaning that the following list refers to the current latest version released under the given channel:
Expected to Fail with the following versions:
v5.3.0
Compare Source
Note: Now trying to follow a standard scheme defined by https://keepachangelog.com/en/1.0.0/
Added
--volume/-v
flag that k3d automatically expandsk3s-storage
->/var/lib/rancher/k3s/storage
k3s-manifests
->/var/lib/rancher/k3s/server/manifests
k3s-manifests-custom
->/var/lib/rancher/k3s/server/manifests/custom
(not K3s default: this is just some sub-directory inside the auto-deploy manifests directory which will also be parsed)k3s-containerd
->/var/lib/rancher/k3s/agent/etc/containerd/config.toml
(use with caution, K3s generates this file!)k3s-containerd-tmpl
->/var/lib/rancher/k3s/agent/etc/containerd/config.toml.tmpl
(used by K3s to generate the real config above)k3s-registry-config
->/etc/rancher/k3s/registries.yaml
(or just use--registry-config
)k3d-
prefix will now be created and managed byk3d
Changed
Fixed
Deprecated
k3d.io/v1alpha3
is now deprecated in favor ofk3d.io/v1alpha4
Removed
cmd/util
, does not affect the CLI (#916)Compatibility
This release was automatically tested with the following setups:
Docker
Expected to Fail with the following versions:
K3s
We test a full cluster lifecycle with different K3s channels, meaning that the following list refers to the current latest version released under the given channel:
Expected to Fail with the following versions:
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.