diff --git a/Makefile b/Makefile index 8dcf362b1..255fed34d 100644 --- a/Makefile +++ b/Makefile @@ -17,7 +17,7 @@ all: container -TAG?=v1.0.0 +TAG?=v1.0.1 PREFIX?=894847497797.dkr.ecr.us-west-2.amazonaws.com/aws-alb-ingress-controller ARCH?=amd64 OS?=linux diff --git a/alb-ingress-controller-helm/Chart.yaml b/alb-ingress-controller-helm/Chart.yaml index 5a727baf9..2b0d3fd91 100644 --- a/alb-ingress-controller-helm/Chart.yaml +++ b/alb-ingress-controller-helm/Chart.yaml @@ -1,5 +1,5 @@ apiVersion: v1 -appVersion: v1.0.0 +appVersion: v1.0.1 description: The ALB Ingress Controller satisfies Kubernetes ingress resources by provisioning Application Load Balancers. engine: gotpl home: https://github.com/kubernetes-sigs/aws-alb-ingress-controller diff --git a/alb-ingress-controller-helm/README.md b/alb-ingress-controller-helm/README.md index cb3ff9d3d..6aa4dc737 100644 --- a/alb-ingress-controller-helm/README.md +++ b/alb-ingress-controller-helm/README.md @@ -49,7 +49,7 @@ The following tables lists the configurable parameters of the alb-ingress-contro | `awsRegion` | AWS region of k8s cluster, required if ec2metadata is unavailable from controller pod | N/A | | `awsVpcID` | AWS VPC ID of k8s cluster, required if ec2metadata is unavailable from controller pod | N/A | | `image.repository` | controller container image repository | `894847497797.dkr.ecr.us-west-2.amazonaws.com/aws-alb-ingress-controller`| -| `image.tag` | controller container image tag | `v1.0.0` | +| `image.tag` | controller container image tag | `v1.0.1` | | `image.pullPolicy` | controller container image pull policy | `IfNotPresent` | | `extraEnv` | map of environment variables to be injected into the controller pod | `{}` | | `nodeSelector` | node labels for controller pod assignment | `{}` | diff --git a/alb-ingress-controller-helm/values.yaml b/alb-ingress-controller-helm/values.yaml index 1a3565666..8b4d66d44 100644 --- a/alb-ingress-controller-helm/values.yaml +++ b/alb-ingress-controller-helm/values.yaml @@ -16,7 +16,7 @@ awsVpcID: "" image: repository: 894847497797.dkr.ecr.us-west-2.amazonaws.com/aws-alb-ingress-controller - tag: "v1.0.0" + tag: "v1.0.1" pullPolicy: IfNotPresent extraArgs: {} diff --git a/docs/README.md b/docs/README.md index 002dc4905..702ac26bb 100644 --- a/docs/README.md +++ b/docs/README.md @@ -5,7 +5,7 @@ # AWS ALB Ingress Controller -**NOTE:** The current image version is `v1.0.0`. Please file any issues you find and note the version used. +**NOTE:** The current image version is `v1.0.1`. Please file any issues you find and note the version used. The AWS ALB Ingress Controller satisfies Kubernetes [ingress resources](https://kubernetes.io/docs/user-guide/ingress) by provisioning [Application Load Balancers](https://docs.aws.amazon.com/elasticloadbalancing/latest/application/introduction.html). diff --git a/docs/examples/alb-ingress-controller.yaml b/docs/examples/alb-ingress-controller.yaml index 736bec4cd..2ee761a21 100644 --- a/docs/examples/alb-ingress-controller.yaml +++ b/docs/examples/alb-ingress-controller.yaml @@ -71,7 +71,7 @@ spec: #- name: AWS_SECRET_ACCESS_KEY # value: SECRETVALUE # Repository location of the ALB Ingress Controller. - image: 894847497797.dkr.ecr.us-west-2.amazonaws.com/aws-alb-ingress-controller:v1.0.0 + image: 894847497797.dkr.ecr.us-west-2.amazonaws.com/aws-alb-ingress-controller:v1.0.1 imagePullPolicy: Always name: server resources: {} diff --git a/docs/guide/controller/setup.md b/docs/guide/controller/setup.md index 8fad7f7f8..9748868d6 100644 --- a/docs/guide/controller/setup.md +++ b/docs/guide/controller/setup.md @@ -27,7 +27,7 @@ You can choose to install ALB ingress controller via Helm or Kubectl ### Kubectl 1. Download sample ALB ingress controller manifest ``` bash - wget https://raw.githubusercontent.com/kubernetes-sigs/aws-alb-ingress-controller/v1.0.0/docs/examples/alb-ingress-controller.yaml + wget https://raw.githubusercontent.com/kubernetes-sigs/aws-alb-ingress-controller/v1.0.1/docs/examples/alb-ingress-controller.yaml ``` 2. Configure the ALB ingress controller manifest @@ -45,7 +45,7 @@ You can choose to install ALB ingress controller via Helm or Kubectl 3. Deploy the RBAC roles manifest ```bash - kubectl apply -f https://raw.githubusercontent.com/kubernetes-sigs/aws-alb-ingress-controller/v1.0.0/docs/examples/rbac-role.yaml + kubectl apply -f https://raw.githubusercontent.com/kubernetes-sigs/aws-alb-ingress-controller/v1.0.1/docs/examples/rbac-role.yaml ``` 4. Deploy the ALB ingress controller manifest diff --git a/docs/guide/external-dns/setup.md b/docs/guide/external-dns/setup.md index 8decb83c6..36bd55de4 100644 --- a/docs/guide/external-dns/setup.md +++ b/docs/guide/external-dns/setup.md @@ -9,7 +9,7 @@ Adequate roles and policies must be configured in AWS and available to the node( 1. Download sample external-dns manifest ``` bash - wget https://raw.githubusercontent.com/kubernetes-sigs/aws-alb-ingress-controller/v1.0.0/docs/examples/external-dns.yaml + wget https://raw.githubusercontent.com/kubernetes-sigs/aws-alb-ingress-controller/v1.0.1/docs/examples/external-dns.yaml ``` 2. Edit the `--domain-filter` flag to include your hosted zone(s) diff --git a/docs/guide/walkthrough/echoserver.md b/docs/guide/walkthrough/echoserver.md index 007730c73..21f7d98f0 100644 --- a/docs/guide/walkthrough/echoserver.md +++ b/docs/guide/walkthrough/echoserver.md @@ -43,8 +43,8 @@ In this walkthrough, you'll 1. Download the example alb-ingress-manifest locally. ```bash - wget https://raw.githubusercontent.com/kubernetes-sigs/aws-alb-ingress-controller/v1.0.0/docs/examples/alb-ingress-controller.yaml - wget https://raw.githubusercontent.com/kubernetes-sigs/aws-alb-ingress-controller/v1.0.0/docs/examples/rbac-role.yaml + wget https://raw.githubusercontent.com/kubernetes-sigs/aws-alb-ingress-controller/v1.0.1/docs/examples/alb-ingress-controller.yaml + wget https://raw.githubusercontent.com/kubernetes-sigs/aws-alb-ingress-controller/v1.0.1/docs/examples/rbac-role.yaml ``` 1. Edit the manifest and set the following parameters and environment variables. @@ -100,9 +100,9 @@ In this walkthrough, you'll 1. Deploy all the echoserver resources (namespace, service, deployment) ```bash - kubectl apply -f https://raw.githubusercontent.com/kubernetes-sigs/aws-alb-ingress-controller/v1.0.0/docs/examples/echoservice/echoserver-namespace.yaml &&\ - kubectl apply -f https://raw.githubusercontent.com/kubernetes-sigs/aws-alb-ingress-controller/v1.0.0/docs/examples/echoservice/echoserver-service.yaml &&\ - kubectl apply -f https://raw.githubusercontent.com/kubernetes-sigs/aws-alb-ingress-controller/v1.0.0/docs/examples/echoservice/echoserver-deployment.yaml + kubectl apply -f https://raw.githubusercontent.com/kubernetes-sigs/aws-alb-ingress-controller/v1.0.1/docs/examples/echoservice/echoserver-namespace.yaml &&\ + kubectl apply -f https://raw.githubusercontent.com/kubernetes-sigs/aws-alb-ingress-controller/v1.0.1/docs/examples/echoservice/echoserver-service.yaml &&\ + kubectl apply -f https://raw.githubusercontent.com/kubernetes-sigs/aws-alb-ingress-controller/v1.0.1/docs/examples/echoservice/echoserver-deployment.yaml ``` 1. List all the resources to ensure they were created. @@ -126,7 +126,7 @@ In this walkthrough, you'll 1. Download the echoserver ingress manifest locally. ```bash - wget https://raw.githubusercontent.com/kubernetes-sigs/aws-alb-ingress-controller/v1.0.0/docs/examples/echoservice/echoserver-ingress.yaml + wget https://raw.githubusercontent.com/kubernetes-sigs/aws-alb-ingress-controller/v1.0.1/docs/examples/echoservice/echoserver-ingress.yaml ``` 1. Configure the subnets, either by add annotation to the ingress or add tags to subnets. @@ -235,7 +235,7 @@ In this walkthrough, you'll 1. Download external-dns to manage Route 53. ```bash - wget https://raw.githubusercontent.com/kubernetes-sigs/aws-alb-ingress-controller/v1.0.0/docs/examples/external-dns.yaml + wget https://raw.githubusercontent.com/kubernetes-sigs/aws-alb-ingress-controller/v1.0.1/docs/examples/external-dns.yaml ``` 1. Edit the `--domain-filter` flag to include your hosted zone(s) @@ -300,7 +300,7 @@ In this walkthrough, you'll follow below steps If you want to use kube2iam to provide the AWS credentials 1. configure the proper policy - The policy to be used can be fetched from https://raw.githubusercontent.com/kubernetes-sigs/aws-alb-ingress-controller/v1.0.0/docs/examples/iam-policy.json + The policy to be used can be fetched from https://raw.githubusercontent.com/kubernetes-sigs/aws-alb-ingress-controller/v1.0.1/docs/examples/iam-policy.json 1. configure the proper role and create the trust relationship You have to find which role is associated woth your K8S nodes. Once you found take note of the full arn: