For the Ubuntu server, nothing. Just do whatever you do to your DNS records/network setup, and reboot the server. It will work as nothing changed.

For the Management Server though, you need to make some changes. The Kubernetes config file qualifies the host by IP address, and not the DNS name. Therefore this file has to be updated.

This file would be typically in two places in the Management Server:

1. {IFSROOT}\config\kube\config
2. %USERPROFILE%\.kube\config

Both these places will have to be updated.

To update the first place, run this in PowerShell:

cd {IFSROOT}
.\main.ps1 -resource 'GETKUBECONFIG'

This will get the new Kubernetes configuration from the MT server and place it in {IFSROOT}\config\kube\config.

Then, you have to copy this file to the second place:

1. PowerShell: copy {IFSROOT}\config\kube\config $HOME\.kube\, or,
2. CMD: copy {IFSROOT}\config\kube\config %USERPROFILE%\.kube\.

That’s it!

Note: {IFSROOT} is the root directory of your management server directory hierarchy, typically called an IFSROOT. You may need to replace the correct path of the directory in the commands.

Hello,

thx for these information, but i have more question:

i’m in 23R1SU22 on-premise environnement, i want to change IP on management, middleware and database.

i follow your instructions for middleware but i have an error on IAM pod, crashloopbackup:

tls: failed to verify certificate: x509: certificate is valid for 10.X.X.X (old one), not 10.X.X.X ( newone )

and one more question, how you declare the new database IP to the midlleware ?

i changed the ip in the ifscloud-values.yaml and i ran the installer.cmd install command, but in my network log i saw that the midlleware tried to connect to the old IP.

Best regards

a little update,

after reran .\main.ps1 -resource 'KEY' and removed the IAM pod, the pod works well.

but still have error  when i try installer.cmd install command and there is no communication between middleware and database