Skip to main content
Solved

kubernetes.io/ingress.class" is deprecated, please use 'spec.ingressClassName' instead


Darshana Herath
Hero (Former Employee)
Forum|alt.badge.img+14

E:\ifsremote\ifsroot\deliveries\build-home\ifsinstaller>installer.cmd --set action=mtinstaller
[Fri May 23 03:58:39 GMT 2025] - INFO: Remote deployment: Parameter logFileLocation added (E:\ifsremote\ifsroot\logs\ifscloudinstaller)
[Fri May 23 03:58:39 GMT 2025] - INFO: Remote deployment: Configuration file found and is added (E:\ifsremote\ifsroot\config\ifscloud-values.yaml)
[Fri May 23 03:58:39 GMT 2025] - INFO: Remote deployment: Solution set file found and is added (E:\ifsremote\ifsroot\deliveries\build-home\ifsinstaller\solutionset.yaml)
[Fri May 23 03:58:39 GMT 2025] - INFO: Installer version: 24.2.4
[Fri May 23 03:58:39 GMT 2025] - INFO: Java: build 11.0.26+4-LTS
[Fri May 23 03:58:39 GMT 2025] - INFO: k8s (client): v1.30.10
[Fri May 23 03:58:39 GMT 2025] - INFO: k8s cluster: https://**.**.**.**:16443
[Fri May 23 03:58:39 GMT 2025] - INFO: k8s (server): v1.30.9
[Fri May 23 03:58:39 GMT 2025] - INFO: helm: v3.15.4
[Fri May 23 03:58:39 GMT 2025] - INFO: ingress: v1.11.4
[Fri May 23 03:58:39 GMT 2025] - INFO: auto scaler: 2.15.0
[Fri May 23 03:58:39 GMT 2025] - INFO: chartVersion not found in properties, using global.helmChartVersion: 242.4.0
[Fri May 23 03:58:39 GMT 2025] - WARNING: Generating self-signed certificate. This will not be persisted.
[Fri May 23 03:58:40 GMT 2025] - INFO: Generating symmetric-keys. These will only be persisted if the secrets, 'symmetric-key' and 'bpa-odata-symmetric-key' does not exist.
[Fri May 23 03:58:40 GMT 2025] - INFO: Creating namespace
[Fri May 23 03:58:46 GMT 2025] - INFO: Repo updated successfully.
[Fri May 23 03:58:46 GMT 2025] - INFO: Using chart ifscloud/ifs-cloud --version 242.4.0
[Fri May 23 03:58:46 GMT 2025] - INFO: Installing ifs-cloud
[Fri May 23 03:58:46 GMT 2025] - INFO: Running helm upgrade
[Fri May 23 04:02:34 GMT 2025] - SEVERE: failed post-install: 1 error occurred:
[Fri May 23 04:02:34 GMT 2025] - SEVERE: Failed to install ifs-cloud
[Fri May 23 04:02:34 GMT 2025] - INFO: Calling MTCTL with arguments: start --namespace **
[Fri May 23 04:02:35 GMT 2025] - SEVERE: Failed to install ifs-cloud. Collected logs from command:
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "ifscloud" chart repository
Update Complete. ÔÄêHappy Helming!ÔÄê
INFO: Repo updated successfully.
INFO: Using chart ifscloud/ifs-cloud --version 242.4.0
INFO: Installing ifs-cloud
INFO: Running helm upgrade
Release "ifs-cloud" does not exist. Installing it now.
W0523 03:58:57.252407    8084 warnings.go:70] annotation "kubernetes.io/ingress.class" is deprecated, please use 'spec.ingressClassName' instead
W0523 03:58:57.256965    8084 warnings.go:70] annotation "kubernetes.io/ingress.class" is deprecated, please use 'spec.ingressClassName' instead
Error: failed post-install: 1 error occurred:
        * job ifs-db-init failed: BackoffLimitExceeded


SEVERE: Failed to install ifs-cloud
INFO: Calling MTCTL with arguments: start --namespace **
IFS Cloud Applications - Middletier Controller
Start deployments
Fri May 23 04:02:35 GMT 2025 L5 - Trying to load scaleObjects......
Fri May 23 04:02:35 GMT 2025 L5 - 0 deployments started

E:\ifsremote\ifsroot\deliveries\build-home\ifsinstaller>

Best answer by rayanhimal

Darshana Herath wrote:

E:\ifsremote\ifsroot\deliveries\build-home\ifsinstaller>installer.cmd --set action=mtinstaller
[Fri May 23 03:58:39 GMT 2025] - INFO: Remote deployment: Parameter logFileLocation added (E:\ifsremote\ifsroot\logs\ifscloudinstaller)
[Fri May 23 03:58:39 GMT 2025] - INFO: Remote deployment: Configuration file found and is added (E:\ifsremote\ifsroot\config\ifscloud-values.yaml)
[Fri May 23 03:58:39 GMT 2025] - INFO: Remote deployment: Solution set file found and is added (E:\ifsremote\ifsroot\deliveries\build-home\ifsinstaller\solutionset.yaml)
[Fri May 23 03:58:39 GMT 2025] - INFO: Installer version: 24.2.4
[Fri May 23 03:58:39 GMT 2025] - INFO: Java: build 11.0.26+4-LTS
[Fri May 23 03:58:39 GMT 2025] - INFO: k8s (client): v1.30.10
[Fri May 23 03:58:39 GMT 2025] - INFO: k8s cluster: https://**.**.**.**:16443
[Fri May 23 03:58:39 GMT 2025] - INFO: k8s (server): v1.30.9
[Fri May 23 03:58:39 GMT 2025] - INFO: helm: v3.15.4
[Fri May 23 03:58:39 GMT 2025] - INFO: ingress: v1.11.4
[Fri May 23 03:58:39 GMT 2025] - INFO: auto scaler: 2.15.0
[Fri May 23 03:58:39 GMT 2025] - INFO: chartVersion not found in properties, using global.helmChartVersion: 242.4.0
[Fri May 23 03:58:39 GMT 2025] - WARNING: Generating self-signed certificate. This will not be persisted.
[Fri May 23 03:58:40 GMT 2025] - INFO: Generating symmetric-keys. These will only be persisted if the secrets, 'symmetric-key' and 'bpa-odata-symmetric-key' does not exist.
[Fri May 23 03:58:40 GMT 2025] - INFO: Creating namespace
[Fri May 23 03:58:46 GMT 2025] - INFO: Repo updated successfully.
[Fri May 23 03:58:46 GMT 2025] - INFO: Using chart ifscloud/ifs-cloud --version 242.4.0
[Fri May 23 03:58:46 GMT 2025] - INFO: Installing ifs-cloud
[Fri May 23 03:58:46 GMT 2025] - INFO: Running helm upgrade
[Fri May 23 04:02:34 GMT 2025] - SEVERE: failed post-install: 1 error occurred:
[Fri May 23 04:02:34 GMT 2025] - SEVERE: Failed to install ifs-cloud
[Fri May 23 04:02:34 GMT 2025] - INFO: Calling MTCTL with arguments: start --namespace **
[Fri May 23 04:02:35 GMT 2025] - SEVERE: Failed to install ifs-cloud. Collected logs from command:
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "ifscloud" chart repository
Update Complete. ÔÄêHappy Helming!ÔÄê
INFO: Repo updated successfully.
INFO: Using chart ifscloud/ifs-cloud --version 242.4.0
INFO: Installing ifs-cloud
INFO: Running helm upgrade
Release "ifs-cloud" does not exist. Installing it now.
W0523 03:58:57.252407    8084 warnings.go:70] annotation "kubernetes.io/ingress.class" is deprecated, please use 'spec.ingressClassName' instead
W0523 03:58:57.256965    8084 warnings.go:70] annotation "kubernetes.io/ingress.class" is deprecated, please use 'spec.ingressClassName' instead
Error: failed post-install: 1 error occurred:
        * job ifs-db-init failed: BackoffLimitExceeded


SEVERE: Failed to install ifs-cloud
INFO: Calling MTCTL with arguments: start --namespace **
IFS Cloud Applications - Middletier Controller
Start deployments
Fri May 23 04:02:35 GMT 2025 L5 - Trying to load scaleObjects......
Fri May 23 04:02:35 GMT 2025 L5 - 0 deployments started

E:\ifsremote\ifsroot\deliveries\build-home\ifsinstaller>

Hi Darshana,

We encountered a similar issue where three ifs-db-init pods were in an Error state, and the ifsiam pod had also failed.

Upon reviewing the logs for the ifs-db-init pods, we identified the following error:


Failed updating database. IO Error: The Network Adapter could not establish the connection.

Failed updating, check credentials.

 

In our case, the root cause was that the database IP (10.1.x.x) fell within the Pod IP range.

Although the following configuration was already set in the main.config.json file:

"PodCidrRange": "10.64.0.0/16",
"LocalNetworkIpRange": "10.1.0.0/16"

 

Pods were still being assigned IPs in the 10.1.x.x range, whereas the expected range was 10.64.x.x.

After the Kubernetes installation and once the kube-system pods were running, we executed the following command:

.\main.ps1 -resource 'CHANGE-POD-IP-RANGE'
 

This updated the Pod IPs to the correct range (10.64.x.x). We then proceeded with the standard setup steps, which resolved the issue for us.

If you are experiencing a similar IP range conflict, we recommend trying the above approach.

Additionally, please ensure that the UFW (Uncomplicated Firewall) on the MT server is not active. If it is, you can disable it at boot using the following commands:

sudo ufw status
sudo ufw disable
 

 

 

 

 

View original
Did this topic help you find an answer to your question?

5 replies

Forum|alt.badge.img+7
  • Sidekick (Partner)
  • 55 replies
  • June 4, 2025

@Darshana Herath 

Hi Darshana,

We also getting the same error with 24R2 SU5. Have you found a solution for this?
 


rayanhimal
Sidekick (Partner)
Forum|alt.badge.img+7
  • Sidekick (Partner)
  • 29 replies
  • Answer
  • June 5, 2025
Darshana Herath wrote:

E:\ifsremote\ifsroot\deliveries\build-home\ifsinstaller>installer.cmd --set action=mtinstaller
[Fri May 23 03:58:39 GMT 2025] - INFO: Remote deployment: Parameter logFileLocation added (E:\ifsremote\ifsroot\logs\ifscloudinstaller)
[Fri May 23 03:58:39 GMT 2025] - INFO: Remote deployment: Configuration file found and is added (E:\ifsremote\ifsroot\config\ifscloud-values.yaml)
[Fri May 23 03:58:39 GMT 2025] - INFO: Remote deployment: Solution set file found and is added (E:\ifsremote\ifsroot\deliveries\build-home\ifsinstaller\solutionset.yaml)
[Fri May 23 03:58:39 GMT 2025] - INFO: Installer version: 24.2.4
[Fri May 23 03:58:39 GMT 2025] - INFO: Java: build 11.0.26+4-LTS
[Fri May 23 03:58:39 GMT 2025] - INFO: k8s (client): v1.30.10
[Fri May 23 03:58:39 GMT 2025] - INFO: k8s cluster: https://**.**.**.**:16443
[Fri May 23 03:58:39 GMT 2025] - INFO: k8s (server): v1.30.9
[Fri May 23 03:58:39 GMT 2025] - INFO: helm: v3.15.4
[Fri May 23 03:58:39 GMT 2025] - INFO: ingress: v1.11.4
[Fri May 23 03:58:39 GMT 2025] - INFO: auto scaler: 2.15.0
[Fri May 23 03:58:39 GMT 2025] - INFO: chartVersion not found in properties, using global.helmChartVersion: 242.4.0
[Fri May 23 03:58:39 GMT 2025] - WARNING: Generating self-signed certificate. This will not be persisted.
[Fri May 23 03:58:40 GMT 2025] - INFO: Generating symmetric-keys. These will only be persisted if the secrets, 'symmetric-key' and 'bpa-odata-symmetric-key' does not exist.
[Fri May 23 03:58:40 GMT 2025] - INFO: Creating namespace
[Fri May 23 03:58:46 GMT 2025] - INFO: Repo updated successfully.
[Fri May 23 03:58:46 GMT 2025] - INFO: Using chart ifscloud/ifs-cloud --version 242.4.0
[Fri May 23 03:58:46 GMT 2025] - INFO: Installing ifs-cloud
[Fri May 23 03:58:46 GMT 2025] - INFO: Running helm upgrade
[Fri May 23 04:02:34 GMT 2025] - SEVERE: failed post-install: 1 error occurred:
[Fri May 23 04:02:34 GMT 2025] - SEVERE: Failed to install ifs-cloud
[Fri May 23 04:02:34 GMT 2025] - INFO: Calling MTCTL with arguments: start --namespace **
[Fri May 23 04:02:35 GMT 2025] - SEVERE: Failed to install ifs-cloud. Collected logs from command:
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "ifscloud" chart repository
Update Complete. ÔÄêHappy Helming!ÔÄê
INFO: Repo updated successfully.
INFO: Using chart ifscloud/ifs-cloud --version 242.4.0
INFO: Installing ifs-cloud
INFO: Running helm upgrade
Release "ifs-cloud" does not exist. Installing it now.
W0523 03:58:57.252407    8084 warnings.go:70] annotation "kubernetes.io/ingress.class" is deprecated, please use 'spec.ingressClassName' instead
W0523 03:58:57.256965    8084 warnings.go:70] annotation "kubernetes.io/ingress.class" is deprecated, please use 'spec.ingressClassName' instead
Error: failed post-install: 1 error occurred:
        * job ifs-db-init failed: BackoffLimitExceeded


SEVERE: Failed to install ifs-cloud
INFO: Calling MTCTL with arguments: start --namespace **
IFS Cloud Applications - Middletier Controller
Start deployments
Fri May 23 04:02:35 GMT 2025 L5 - Trying to load scaleObjects......
Fri May 23 04:02:35 GMT 2025 L5 - 0 deployments started

E:\ifsremote\ifsroot\deliveries\build-home\ifsinstaller>

Hi Darshana,

We encountered a similar issue where three ifs-db-init pods were in an Error state, and the ifsiam pod had also failed.

Upon reviewing the logs for the ifs-db-init pods, we identified the following error:


Failed updating database. IO Error: The Network Adapter could not establish the connection.

Failed updating, check credentials.

 

In our case, the root cause was that the database IP (10.1.x.x) fell within the Pod IP range.

Although the following configuration was already set in the main.config.json file:

"PodCidrRange": "10.64.0.0/16",
"LocalNetworkIpRange": "10.1.0.0/16"

 

Pods were still being assigned IPs in the 10.1.x.x range, whereas the expected range was 10.64.x.x.

After the Kubernetes installation and once the kube-system pods were running, we executed the following command:

.\main.ps1 -resource 'CHANGE-POD-IP-RANGE'
 

This updated the Pod IPs to the correct range (10.64.x.x). We then proceeded with the standard setup steps, which resolved the issue for us.

If you are experiencing a similar IP range conflict, we recommend trying the above approach.

Additionally, please ensure that the UFW (Uncomplicated Firewall) on the MT server is not active. If it is, you can disable it at boot using the following commands:

sudo ufw status
sudo ufw disable
 

 

 

 

 


Darshana Herath
Hero (Former Employee)
Forum|alt.badge.img+14
  • Author
  • Hero (Former Employee)
  • 119 replies
  • June 11, 2025
HashanD wrote:

@Darshana Herath 

Hi Darshana,

We also getting the same error with 24R2 SU5. Have you found a solution for this?
 

Check the log, in my case, IFSSYS had locked

 

kubectl logs ifs-db-init-XXX -c ifs-db-init -n <NAMESPASE>

Failed updating database. ORA-28000: The account is locked..


Darshana Herath
Hero (Former Employee)
Forum|alt.badge.img+14
  • Author
  • Hero (Former Employee)
  • 119 replies
  • June 11, 2025
rayanhimal wrote:
Darshana Herath wrote:

E:\ifsremote\ifsroot\deliveries\build-home\ifsinstaller>installer.cmd --set action=mtinstaller
[Fri May 23 03:58:39 GMT 2025] - INFO: Remote deployment: Parameter logFileLocation added (E:\ifsremote\ifsroot\logs\ifscloudinstaller)
[Fri May 23 03:58:39 GMT 2025] - INFO: Remote deployment: Configuration file found and is added (E:\ifsremote\ifsroot\config\ifscloud-values.yaml)
[Fri May 23 03:58:39 GMT 2025] - INFO: Remote deployment: Solution set file found and is added (E:\ifsremote\ifsroot\deliveries\build-home\ifsinstaller\solutionset.yaml)
[Fri May 23 03:58:39 GMT 2025] - INFO: Installer version: 24.2.4
[Fri May 23 03:58:39 GMT 2025] - INFO: Java: build 11.0.26+4-LTS
[Fri May 23 03:58:39 GMT 2025] - INFO: k8s (client): v1.30.10
[Fri May 23 03:58:39 GMT 2025] - INFO: k8s cluster: https://**.**.**.**:16443
[Fri May 23 03:58:39 GMT 2025] - INFO: k8s (server): v1.30.9
[Fri May 23 03:58:39 GMT 2025] - INFO: helm: v3.15.4
[Fri May 23 03:58:39 GMT 2025] - INFO: ingress: v1.11.4
[Fri May 23 03:58:39 GMT 2025] - INFO: auto scaler: 2.15.0
[Fri May 23 03:58:39 GMT 2025] - INFO: chartVersion not found in properties, using global.helmChartVersion: 242.4.0
[Fri May 23 03:58:39 GMT 2025] - WARNING: Generating self-signed certificate. This will not be persisted.
[Fri May 23 03:58:40 GMT 2025] - INFO: Generating symmetric-keys. These will only be persisted if the secrets, 'symmetric-key' and 'bpa-odata-symmetric-key' does not exist.
[Fri May 23 03:58:40 GMT 2025] - INFO: Creating namespace
[Fri May 23 03:58:46 GMT 2025] - INFO: Repo updated successfully.
[Fri May 23 03:58:46 GMT 2025] - INFO: Using chart ifscloud/ifs-cloud --version 242.4.0
[Fri May 23 03:58:46 GMT 2025] - INFO: Installing ifs-cloud
[Fri May 23 03:58:46 GMT 2025] - INFO: Running helm upgrade
[Fri May 23 04:02:34 GMT 2025] - SEVERE: failed post-install: 1 error occurred:
[Fri May 23 04:02:34 GMT 2025] - SEVERE: Failed to install ifs-cloud
[Fri May 23 04:02:34 GMT 2025] - INFO: Calling MTCTL with arguments: start --namespace **
[Fri May 23 04:02:35 GMT 2025] - SEVERE: Failed to install ifs-cloud. Collected logs from command:
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "ifscloud" chart repository
Update Complete. ÔÄêHappy Helming!ÔÄê
INFO: Repo updated successfully.
INFO: Using chart ifscloud/ifs-cloud --version 242.4.0
INFO: Installing ifs-cloud
INFO: Running helm upgrade
Release "ifs-cloud" does not exist. Installing it now.
W0523 03:58:57.252407    8084 warnings.go:70] annotation "kubernetes.io/ingress.class" is deprecated, please use 'spec.ingressClassName' instead
W0523 03:58:57.256965    8084 warnings.go:70] annotation "kubernetes.io/ingress.class" is deprecated, please use 'spec.ingressClassName' instead
Error: failed post-install: 1 error occurred:
        * job ifs-db-init failed: BackoffLimitExceeded


SEVERE: Failed to install ifs-cloud
INFO: Calling MTCTL with arguments: start --namespace **
IFS Cloud Applications - Middletier Controller
Start deployments
Fri May 23 04:02:35 GMT 2025 L5 - Trying to load scaleObjects......
Fri May 23 04:02:35 GMT 2025 L5 - 0 deployments started

E:\ifsremote\ifsroot\deliveries\build-home\ifsinstaller>

Hi Darshana,

We encountered a similar issue where three ifs-db-init pods were in an Error state, and the ifsiam pod had also failed.

Upon reviewing the logs for the ifs-db-init pods, we identified the following error:


Failed updating database. IO Error: The Network Adapter could not establish the connection.

Failed updating, check credentials.

 

In our case, the root cause was that the database IP (10.1.x.x) fell within the Pod IP range.

Although the following configuration was already set in the main.config.json file:

"PodCidrRange": "10.64.0.0/16",
"LocalNetworkIpRange": "10.1.0.0/16"

 

Pods were still being assigned IPs in the 10.1.x.x range, whereas the expected range was 10.64.x.x.

After the Kubernetes installation and once the kube-system pods were running, we executed the following command:

.\main.ps1 -resource 'CHANGE-POD-IP-RANGE'
 

This updated the Pod IPs to the correct range (10.64.x.x). We then proceeded with the standard setup steps, which resolved the issue for us.

If you are experiencing a similar IP range conflict, we recommend trying the above approach.

Additionally, please ensure that the UFW (Uncomplicated Firewall) on the MT server is not active. If it is, you can disable it at boot using the following commands:

sudo ufw status
sudo ufw disable
 

 

 

 

 

Thank you very much for the information, in my case, IFSSYS had locked, 
 

kubectl logs ifs-db-init-XXX -c ifs-db-init -n <NAMESPASE>

Failed updating database. ORA-28000: The account is locked..


Forum|alt.badge.img+7
  • Sidekick (Partner)
  • 55 replies
  • June 11, 2025
Darshana Herath wrote:
HashanD wrote:

@Darshana Herath 

Hi Darshana,

We also getting the same error with 24R2 SU5. Have you found a solution for this?
 

Check the log, in my case, IFSSYS had locked

 

kubectl logs ifs-db-init-XXX -c ifs-db-init -n <NAMESPASE>

Failed updating database. ORA-28000: The account is locked..

Thank you
In our case we had the issue with PodCidrRange


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings