Skip to content

Commit

Permalink
Release 4.0.0 (#4)
Browse files Browse the repository at this point in the history
* Update Readme

* Bump version and merge main

* Update README
  • Loading branch information
rwilson-release committed May 2, 2024
1 parent b3ea0d3 commit 1728feb
Show file tree
Hide file tree
Showing 4 changed files with 95 additions and 27 deletions.
6 changes: 3 additions & 3 deletions Chart.yaml
Original file line number Diff line number Diff line change
@@ -1,12 +1,12 @@
apiVersion: v2
description: Nginx Ingress
name: release-ingress
version: 3.1.0
version: 4.0.0
icon: https://avatars.githubusercontent.com/u/71455204?s=200&v=4
home: https://releasehub.com
maintainers:
- name: ReleaseHub
email: hello@releasehub.com
- name: Release
email: hello@release.com
sources:
- https://github.com/releasehub-com/helm-ingress
keywords:
Expand Down
64 changes: 48 additions & 16 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,25 +14,12 @@ charts:
values: values.yaml
```

# IMPORTANT VERSION INFORMATION

Kubernetes has deprecated the API for `ingress` type as of v1.19 and removed the [deprecated version](https://kubernetes.io/blog/2021/07/14/upcoming-changes-in-kubernetes-1-22/#what-to-do) as of v1.22.
We have introduced this breaking change internally for all customers who upgrade to v1.21. This means that you should use the v1.20 tag for cluster versions up to v1.20 and use the main branch or later releases
for versions v1.21 and above. The reason for this change is that customers who use v1.20 of the chart will be able to upgrade to v1.21 of Kubernetes without breaking any existing ingress charts. Once upgraded,
the v1.21 chart will need to be used for any new ingress templates. This gives customers a smooth upgrade path without breaking exisitng infrastructure and applications. When v1.22 and above are available,
customers will be able to use only the new chart version.

The example for using v1.20 is similar to the above:
```yaml
charts:
- name: <service>-ingress
version: 2.1.0
...
```

# Values File Example
To use the Helm chart you will need to have a `values.yaml` file located in your source control repository. You will need to customize the `values.yaml` file to reference the service that you would like to expose to the Internet.

## Single Ingress
> There are two supported methods for adding ingresses. The single method as follows:
```yaml
service:
name: frontend
Expand All @@ -44,3 +31,48 @@ ingress:
kubernetes.io/ingress.class: nginx
nginx.ingress.kubernetes.io/force-ssl-redirect: "true"
```

## Multiple Ingresses
> And the multiple list method as follows:
```yaml
services:
- service:
name: frontend
externalPort: 8080
ingress:
hosts:
- ${FRONTEND_INGRESS_HOST}
annotations:
kubernetes.io/ingress.class: nginx
nginx.ingress.kubernetes.io/force-ssl-redirect: "true"
- service:
name: backend
externalPort: 3000
ingress:
hosts:
- ${BACKEND_INGRESS_HOST}
annotations:
kubernetes.io/ingress.class: nginx
```

> You can use both!!
# IMPORTANT VERSION INFORMATION
## Matrix chart

| Chart Version | Kubernetes Versions | Chart status | repo_url (to pin) |
|:-------------:|:-------------------:|:------------------:|:---------------------------------------------------------------------|
| 4.0.0 | 1.19+ | :white_check_mark: | https://raw.githubusercontent.com/releasehub-com/helm-ingress/4.0.0/ |
| 3.1.0 | 1.19+ | :white_check_mark: | https://raw.githubusercontent.com/releasehub-com/helm-ingress/3.1.0/ |
| 3.0.0 | 1.14+ | :warning: | https://raw.githubusercontent.com/releasehub-com/helm-ingress/3.0.0/ |
| 2.1.1 | 1.14 - 1.21 | :x: | https://raw.githubusercontent.com/releasehub-com/helm-ingress/2.1.1/ |
| 1.2.0 | 1.14 - 1.21 | :x: | https://raw.githubusercontent.com/releasehub-com/helm-ingress/1.2.0/ |


## Chart versions 1.x and 2.x are EOL and this chart is compatible with K8s 1.19+ only
~~Kubernetes has deprecated the API for `ingress` type as of v1.19 and removed the [deprecated version](https://kubernetes.io/blog/2021/07/14/upcoming-changes-in-kubernetes-1-22/#what-to-do) as of v1.22.
We have introduced this breaking change internally for all customers who upgrade to v1.21. This means that you should use the v1.20 tag for cluster versions up to v1.20 and use the main branch or later releases
for versions v1.21 and above. The reason for this change is that customers who use v1.20 of the chart will be able to upgrade to v1.21 of Kubernetes without breaking any existing ingress charts. Once upgraded,
the v1.21 chart will need to be used for any new ingress templates. This gives customers a smooth upgrade path without breaking exisitng infrastructure and applications. When v1.22 and above are available,
customers will be able to use only the new chart version.~~
52 changes: 44 additions & 8 deletions index.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,25 @@ apiVersion: v1
entries:
release-ingress:
- apiVersion: v2
created: "2022-08-13T13:03:50.5833935-07:00"
created: "2023-09-19T17:11:47.325516243-07:00"
description: Nginx Ingress
digest: 4c6a2e90cf18f04d553134d8d23fc0f3adbab7b57e7fecda1b5413bc872719cb
home: https://release.com
icon: https://avatars.githubusercontent.com/u/71455204?s=200&v=4
keywords:
- helm
- ingress
maintainers:
- email: [email protected]
name: Release
name: release-ingress
sources:
- https://github.com/releasehub-com/helm-ingress
urls:
- https://raw.githubusercontent.com/releasehub-com/helm-ingress/release-4.0.0/release-ingress-4.0.0.tgz
version: 4.0.0
- apiVersion: v2
created: "2023-09-19T17:11:47.325516243-07:00"
description: Nginx Ingress
digest: d9244a34730ae81a1defb0cc126182101986c6801a3b898ba7b9661d1faa4cbd
home: https://releasehub.com
Expand All @@ -20,16 +38,34 @@ entries:
- https://raw.githubusercontent.com/releasehub-com/helm-ingress/release-3.1.0/release-ingress-3.1.0.tgz
version: 3.1.0
- apiVersion: v2
created: "2022-08-13T13:03:50.5827437-07:00"
created: "2023-09-19T17:11:47.325213343-07:00"
description: Nginx Ingress
digest: d9244a34730ae81a1defb0cc126182101986c6801a3b898ba7b9661d1faa4cbd
home: https://release.com
icon: https://avatars.githubusercontent.com/u/71455204?s=200&v=4
keywords:
- helm
- ingress
maintainers:
- email: [email protected]
name: ReleaseHub
name: release-ingress
sources:
- https://github.com/releasehub-com/helm-ingress
urls:
- https://raw.githubusercontent.com/releasehub-com/helm-ingress/main/release-ingress-3.1.0.tgz
version: 3.1.0
- apiVersion: v2
created: "2023-09-19T17:11:47.324591244-07:00"
description: Nginx Ingress
digest: 0dfe686e8b68e2ff76a657b28fae11098dcfce4e4c4ffd1328fba934941dfdbd
home: https://releasehub.com
home: https://release.com
icon: https://avatars.githubusercontent.com/u/71455204?s=200&v=4
keywords:
- helm
- ingress
maintainers:
- email: hello@releasehub.com
- email: hello@release.com
name: ReleaseHub
name: release-ingress
sources:
Expand All @@ -38,21 +74,21 @@ entries:
- https://raw.githubusercontent.com/releasehub-com/helm-ingress/main/release-ingress-3.0.0.tgz
version: 3.0.0
- apiVersion: v1
created: "2022-08-13T13:03:50.5824122-07:00"
created: "2023-09-19T17:11:47.324229044-07:00"
description: Nginx Ingress
digest: 4eda4ecf43cf654367a694d35a5aa4cc67ea28ae2b8fb22325a6dc2f843bacff
home: https://releasehub.com
home: https://release.com
icon: https://avatars.githubusercontent.com/u/71455204?s=200&v=4
keywords:
- helm
- ingress
maintainers:
- email: hello@releasehub.com
- email: hello@release.com
name: ReleaseHub
name: release-ingress
sources:
- https://github.com/releasehub-com/helm-ingress
urls:
- https://raw.githubusercontent.com/releasehub-com/helm-ingress/main/release-ingress-2.1.0.tgz
version: 2.1.0
generated: "2022-08-13T13:03:50.5820698-07:00"
generated: "2023-09-19T17:11:47.314606247-07:00"
Binary file added release-ingress-4.0.0.tgz
Binary file not shown.

0 comments on commit 1728feb

Please sign in to comment.