Hello,

 

I have spent last week on modifying nginx-ingress component in oom
repository to be more offline friendly
<https://jira.onap.org/browse/OOM-2050> OOM-2050 

Right now repo and images are downloaded in runtime). 

 

There are multiple ways of adding nginx-ingress, we need to decide which one
is better: 

Option 1) First option is to manually download nginx-ingress repository
beside other components into oom/kubernetes/ directory

                  and modify oom/kubernetes/onap/requirements.yaml with
@local repository (it is what I have already done in
https://gerrit.onap.org/r/#/c/oom/+/93872/)
                  But there are lot of inconsistency in later usage. Version
of this repository needs to be manually checked and update if needed. It
means it is unusable basically.

 

Option 2) Other option here is to add nginx-ingress repo as submodule into
oom repository. The problem here is that the repository is on github, so not
sure how it would work together with onap gerrit.

 

both (1) and (2) will also allow Lucjan and guys to continue configuring
nginx-ingress from OOM perspective

https://gerrit.onap.org/r/#/c/oom/+/93748/

https://gerrit.onap.org/r/#/c/oom/+/93749/

https://gerrit.onap.org/r/#/c/oom/+/93750/

 

Option 3) Last option which come to our mind is to add this nginx-ingress
directly into RKE. As I find out by default nginx-ingress is part of RKE.
But it is not enabled by default ! 

                  I have checked oom/offline-installer and I can see that we
downloading nginx-ingress images which are basically the same as in github
repo Lucjan used first. 

 

Below are two images which are taken from
offline-installer/ansible/roles/rke/defaults/main.yml:

 

ingress: rancher/nginx-ingress-controller:0.21.0-rancher3

ingress_backend:
rancher/nginx-ingress-controller-defaultbackend:1.4-rancher1

 

 

And here is blank configuration for ingress directly in RKE taken from
offline-installer/ansible/roles/rke/templates/cluster.yml.j2:

 

ingress:

provider: ""

options: {}

node_selector: {}

extra_args: {}

 

 

https://www.cnrancher.com/blog/2018/2018-09-13-load-balancing-options-2dot0/

https://rancher.com/docs/rke/latest/en/config-options/add-ons/ingress-contro
llers/?__hstc=220764231.af5d3a08163656e5588399a68a7d6fb4.1566285435689.15662
85435689.1566285435689.1
<https://rancher.com/docs/rke/latest/en/config-options/add-ons/ingress-contr
ollers/?__hstc=220764231.af5d3a08163656e5588399a68a7d6fb4.1566285435689.1566
285435689.1566285435689.1&__hssc=220764231.1.1566285435689&__hsfp=1103756939
> &__hssc=220764231.1.1566285435689&__hsfp=1103756939

 

              choosing (3) will probably means to remove nginx-ingress
feature from OOM and add it purely into RKE, we can do it for the offline
installer and adapt

              RKE instructions in
https://docs.onap.org/en/latest/submodules/oom.git/docs/oom_setup_kubernetes
_rancher.html#onap-on-kubernetes-with-rancher

 

 

we believe that (3) is probably better but if we would really like to
enforce this feature it's probably safer to have is done in OOM (2),

any suggestions welcome !!

 

Thanks,

Ondrej & Michal

 

 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#18630): https://lists.onap.org/g/onap-discuss/message/18630
Mute This Topic: https://lists.onap.org/mt/32967870/21656
Group Owner: [email protected]
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub  
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to