You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* CIS supports IP address assignment to Virtual Server CRD using `F5 IPAM Controller <https://github.com/f5devcentral/f5-ipam-controller/releases>`_. Refer for `Examples <https://github.com/f5devcentral/f5-ipam-controller/blob/main/README.md>`_.
9
+
* CIS allows user to leverage Virtual IP address using either `F5 IPAM Controller <https://github.com/f5devcentral/f5-ipam-controller/releases>`_ or virtualServerAddress field in VirtualServer CRD
10
+
* Support Passthrough termination for TLS CRD
11
+
* Added support for AS3 schema minor versions
12
+
* :issues:`1631` Support `caCertificate` for OpenShift Routes
13
+
* :issues:`1571` iRule reference for VirtualServer CRDs
14
+
* :issues:`1592` :issues:`1621` Enabling VLANS for VirtualServer and TransportServer CRDs
15
+
* Updated CR Kind from `NginxCisConnector` to `IngressLink`
16
+
* Helm Chart Enhancements:
17
+
- Added Support for `livenessProbe <https://github.com/F5Networks/charts/issues/34>`_, `ReadinessProbe <https://github.com/F5Networks/charts/issues/34>`_, `nodeSelectors <https://github.com/F5Networks/charts/issues/38>`_, `tolerations <https://github.com/F5Networks/charts/issues/38>`_.
18
+
- :issues:`1632` Added Support for skipping CRDs.
10
19
11
20
Bug Fixes
12
21
`````````
13
-
* :issues:`1457` Each Client request will be logged on BIG-IP when http2-profile is associated to VS
14
-
* :issues:`1498` In iRule openshift_passthrough_irule the variable "$dflt_pool" could not be set correctly when http/2-profile is linked to VS
15
-
* :issues:`1458` CISv2.1.0 does not delete LTM-Policy reset-rule when OpenShift-annotation for whitelist-source-range will be removed
22
+
* :issues:`1457` Each Client request get logged on BIG-IP when http2-profile associated to VS
23
+
* :issues:`1458` CISv2.1.0 does not delete LTM-Policy reset-rule when removed the whitelist-source-range OpenShift annotation
24
+
* :issues:`1498` openshift_passthrough_irule could not set the variable "$dflt_pool" correctly when http/2-profile linked to VS
25
+
* :issues:`1565` Logs should distinguish configmap and Ingress errors
26
+
* :issues:`1641` Debug log sKey.ServiceName in syncVirtualServer
@@ -219,7 +235,7 @@ Archived CF and Mesos Github repos
219
235
Guidelines for upgrading to CIS 2.1
220
236
```````````````````````````````````
221
237
* Those migrating from agent CCCL to agent AS3 :
222
-
- User should clean up LTM resources in BIG-IP partition created by CCCL before migrating to CIS 2.1.
238
+
- User should clean up LTM resources in BIG-IP partition created by CCCL before migrating to CIS 2.1.
223
239
Steps to clean up LTM resources in BIG-IP partition using AS3
224
240
* Use below POST call along with this `AS3 declaration <https://raw.githubusercontent.com/F5Networks/k8s-bigip-ctlr/master/docs/_static/config_examples/example-empty-AS3-declaration.yaml>`_.
225
241
- mgmt/shared/appsvcs/declare
@@ -257,14 +273,14 @@ Bug Fixes
257
273
* :issues:`1233` CIS handles ClientSSL annotation and cert/key logging issues.
258
274
* :issues:`1145,1185,1295` CIS handles namespace isolation for AS3 configmaps.
- `--manage-ingress-class-only` A flag whether to handle Ingresses that do not have the class annotation and with annotation `kubernetes.io/ingress.class` set to `f5`. When set `true`, process ingress resources with `kubernetes.io/ingress.class` set to `f5` or custom ingress class.
313
329
- `--ingress-class` to define custom ingress class to watch.
314
330
- `--filter-tenants` A flag whether to enable tenant filtering in BIG-IP.
315
-
* CIS pushes AS3 Configuration after 3 seconds when encounters 503 HTTP response code from BIG-IP.
316
-
* CIS does not push AS3 configuration when encounters 404 HTTP response code from BIG-IP.
331
+
* CIS pushes AS3 Configuration after 3 seconds when encounters 503 HTTP response code from BIG-IP.
332
+
* CIS does not push AS3 configuration when encounters 404 HTTP response code from BIG-IP.
317
333
318
334
Bug Fixes
319
335
`````````
@@ -369,7 +385,7 @@ Added Functionality
369
385
* Added support for OpenShift version 4.1.
370
386
- | Controller service account needs ``cluster-admin`` role. Before upgrading controller to v1.11.0 and above, update cluster role as follows:
* In the Name field, type name as "Proxy_Protocol_iRule".
30
-
* In the Definition field, Copy the definition from [Proxy_Protocol_iRule](https://raw.githubusercontent.com/F5Networks/k8s-bigip-ctlr/doc/docs/_static/config_examples/crd/IngressLink/Proxy_Protocol_iRule) file.
30
+
* In the Definition field, Copy the definition from [Proxy_Protocol_iRule](https://raw.githubusercontent.com/F5Networks/k8s-bigip-ctlr/master/docs/_static/config_examples/crd/IngressLink/Proxy_Protocol_iRule) file.
31
31
* Click Finished.
32
32
33
-
### 3. Install the CIS Controller
33
+
### 3. Install the CIS Controller
34
34
35
35
* Refer to [CIS Installation guide](https://clouddocs.f5.com/containers/latest/userguide/cis-helm.html) to install Container Ingress Services on Kubernetes or Openshift
36
36
* Make sure that you deployed CIS in CRD mode (use "--custom-resource-mode=true" and "--ingress-link-mode=true" in your CIS Configuration. This is specific to this preview)
37
37
38
38
### 4. Install the Nginx Ingress Controller
39
39
40
-
* Refer to [Integration with F5 Container Ingress Services](https://github.com/nginxinc/kubernetes-ingress/blob/master/docs-web/integration-with-cis.md#1-install-the-ingress-controller-with-the-integration-enabled) to deploy NGINX Ingress Controller
40
+
* Refer to [Integration with F5 Container Ingress Services](https://github.com/nginxinc/kubernetes-ingress/blob/master/docs-web/integration-with-cis.md) to deploy NGINX Ingress Controller
* Update the "virtualServerAddress" parameter in the ingresslink.yaml resource. This IP address will be used to configure the BIG-IP device. It will be used to accept traffic and load balance it among the NGINX Ingress Controller pods.
49
49
50
-
```kubectl apply -f ingresslink.yaml```
50
+
```kubectl apply -f ingresslink.yaml```
51
51
52
-
##### Note:
52
+
##### Note:
53
53
1. The name of the app label selector in IngressLink resource should match the labels of the service which exposes the NGINX Ingress Controller.
54
54
2. The service which exposes the NGINX Ingress Controller should be of type nodeport.
55
55
@@ -69,7 +69,7 @@ Let's test the traffic (in this example we used 192.168.10.5 as our VirtualServe
69
69
Server address: 10.12.0.18:80
70
70
Server name: coffee-7586895968-r26zn
71
71
...
72
-
72
+
73
73
Also, if you check the status of the cafe-ingress, you will see the IP of the VirtualServerAddress (in this example we used 192.168.10.5 as our VirtualServerAddress):
0 commit comments