Skip to content

Commit

Permalink
Remove Unused Packages
Browse files Browse the repository at this point in the history
  • Loading branch information
rossedman committed Oct 6, 2021
1 parent dc8a79d commit b950a6b
Show file tree
Hide file tree
Showing 2,628 changed files with 139 additions and 929,577 deletions.
8 changes: 0 additions & 8 deletions .buildkite/pipeline.yml

This file was deleted.

1 change: 1 addition & 0 deletions .gitignore
Original file line number Diff line number Diff line change
@@ -1,2 +1,3 @@
bin/*
coverage.out
coverage.txt
64 changes: 2 additions & 62 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,14 +2,7 @@

![example](preview.png)

A kubectl plugin that checks your clusters for component compatibility and Kubernetes version end of life. This plugin is meant to assist with the upgrade process for these needs:

- Assessing what components need to be upgraded before upgrading to a specific Kubernetes version
- Assessing how much time is available before the Kubernetes version is sunsetted in different platforms like EKS

This cluster is _not_ responsible for

- Finding deprecated APIs, other tools can do this well, like `kubent`
A kubectl plugin that checks your clusters for component compatibility and Kubernetes version end of life. This plugin is meant to assess how much time is available before the Kubernetes version is sunsetted in different platforms like EKS

## Quickstart

Expand All @@ -22,7 +15,7 @@ make install
Once installed you can now run

```
kubectl check
kubectl endoflife
```

## Commands
Expand Down Expand Up @@ -64,57 +57,4 @@ In the first example we have set anything less than 200 days to be expired and e
if ! kubectl check endoflife --product amazon-eks --silent --expiry-range 30 ; then
echo "starting upgrade now..."
fi
```

### kubectl check versions

This will check the component versions and what version they require to upgrade to
another version of Kubernetes, this uses the config located at `cmd/config` and can support
multiple Kubernetes versions

```
❯ kubectl check versions --kube-version v1.19
SERVICE OUT OF DATE CURRENT VERSION REQUIRED VERSION
cluster-autoscaler false v1.19.1 1.19.0
coredns false latest 1.8.4
kube-state-metrics false v2.1.0 2.1.0
metrics-server false v0.5.0 0.5.0
kube-proxy false v1.19.6-eksbuild.2 1.19.6-eksbuild.2
node-problem-detector false v0.8.9 0.8.9
cert-manager false v1.4.0 1.4.0
```

---

## Version Config

This configuration is highly configurable, here is an example of a simple configuration that has version compatbility for `coredns` across multiple Kubernetes releases.

```json
{
"v1.19": [
{
"Name": "coredns",
"Version": "1.7.0"
}
],
"v1.20": [
{
"Name": "coredns",
"Version": "1.7.0"
}
],
"v1.21": [
{
"Name": "coredns",
"Version": "1.8.0"
}
],
"v1.22": [
{
"Name": "coredns",
"Version": "1.8.4"
}
]
}
```
19 changes: 0 additions & 19 deletions TODO.md

This file was deleted.

146 changes: 0 additions & 146 deletions cmd/check_endoflife.go

This file was deleted.

Loading

0 comments on commit b950a6b

Please sign in to comment.