-
Notifications
You must be signed in to change notification settings - Fork 98
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: doriordan/skuber
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v3.0.0-beta7
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: doriordan/skuber
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v3.0.0
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 19 commits
- 151 files changed
- 2 contributors
Commits on Oct 24, 2025
-
Configuration menu - View commit details
-
Copy full SHA for 59ad395 - Browse repository at this point
Copy the full SHA 59ad395View commit details
Commits on Oct 26, 2025
-
Configuration menu - View commit details
-
Copy full SHA for 908e143 - Browse repository at this point
Copy the full SHA 908e143View commit details
Commits on Nov 3, 2025
-
Configuration menu - View commit details
-
Copy full SHA for dd11cae - Browse repository at this point
Copy the full SHA dd11caeView commit details
Commits on Nov 5, 2025
-
Fixed error on missing config references (#425)
It is possible for kube config file to contain a context that refers to cluster or user configurations that don't exist. I don't know how, but my kubeconfig file does, and even when I clean it up, this frequently happens. These contexts are old contexts that I don't use anymore, so they are safe to ignore. kubectl just ignores them. Skuber should do the same.
Configuration menu - View commit details
-
Copy full SHA for 633e502 - Browse repository at this point
Copy the full SHA 633e502View commit details
Commits on Nov 10, 2025
-
Allow async auth providers (#424)
This adds support for async auth providers. There are many use cases for this, for example, authenticating with Kubernetes in AWS but outside of EKS, you need to make API calls to get a frequently rotated token. This allows that token to be looked up in a non blocking way. This also prepares the way for better support for reloading tokens in Kubernetes itself given that they are now frequently rotated.
Configuration menu - View commit details
-
Copy full SHA for 6ddbcfa - Browse repository at this point
Copy the full SHA 6ddbcfaView commit details -
feat: reload access tokens for in cluster config (#426)
Fixes #350 This implements token reloading for in cluster config. It's built on #424 so that needs to be reviewed/merged first. Also fixed a resource leak where the input streams for reading the files for in cluster config were not being closed. This was necessary to fix given that we're now frequently loading those streams.
Configuration menu - View commit details
-
Copy full SHA for d482713 - Browse repository at this point
Copy the full SHA d482713View commit details -
Configuration menu - View commit details
-
Copy full SHA for 124944f - Browse repository at this point
Copy the full SHA 124944fView commit details -
Configuration menu - View commit details
-
Copy full SHA for 55c597d - Browse repository at this point
Copy the full SHA 55c597dView commit details
Commits on Nov 11, 2025
-
Configuration menu - View commit details
-
Copy full SHA for bbd7537 - Browse repository at this point
Copy the full SHA bbd7537View commit details
Commits on Nov 16, 2025
-
Configuration menu - View commit details
-
Copy full SHA for 33a05dc - Browse repository at this point
Copy the full SHA 33a05dcView commit details
Commits on Nov 17, 2025
-
Configuration menu - View commit details
-
Copy full SHA for 08523a6 - Browse repository at this point
Copy the full SHA 08523a6View commit details
Commits on Nov 18, 2025
-
Configuration menu - View commit details
-
Copy full SHA for f469ddd - Browse repository at this point
Copy the full SHA f469dddView commit details -
Configuration menu - View commit details
-
Copy full SHA for 33a2bb9 - Browse repository at this point
Copy the full SHA 33a2bb9View commit details -
Configuration menu - View commit details
-
Copy full SHA for faadf54 - Browse repository at this point
Copy the full SHA faadf54View commit details
Commits on Nov 19, 2025
-
Cherrypick of Addition Of SubjectAccessReview API (#429) into 3.0
Also removed legacy beta versions of apps group
Configuration menu - View commit details
-
Copy full SHA for a8e51c6 - Browse repository at this point
Copy the full SHA a8e51c6View commit details -
Configuration menu - View commit details
-
Copy full SHA for cb2dbfa - Browse repository at this point
Copy the full SHA cb2dbfaView commit details -
Configuration menu - View commit details
-
Copy full SHA for de075d6 - Browse repository at this point
Copy the full SHA de075d6View commit details -
Configuration menu - View commit details
-
Copy full SHA for 22eeaf9 - Browse repository at this point
Copy the full SHA 22eeaf9View commit details -
Configuration menu - View commit details
-
Copy full SHA for b03537e - Browse repository at this point
Copy the full SHA b03537eView commit details
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v3.0.0-beta7...v3.0.0