[DNM] [release-4.15] Fix collecting IPsec data for upgrade #483
Conversation
After IPsec is upgraded from 4.14 into later versions, API option for IPsec in
networks.operator.openshift.io cluster object continues to have {} in the ipsecConfig
and may not be migrated to newer version containing IPsec mode option. This is supported
in OCP for backward compatibility, so mg needs fixing to collect ipsec data when API
configured with old option.
Signed-off-by: Periyasamy Palanisamy <[email protected]>
(cherry picked from commit e4e2e33)
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: pperiyasamy The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/assign @huiran0826 |
|
@pperiyasamy: all tests passed! Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
After IPsec is upgraded from 4.14 into later versions, API option for IPsec in networks.operator.openshift.io cluster object continues to have {} in the ipsecConfig and may not be migrated to newer version containing IPsec mode option. This is supported in OCP for backward compatibility, so mg needs fixing to collect ipsec data when API configured with old option.
Signed-off-by: Periyasamy Palanisamy [email protected]
(cherry picked from commit e4e2e33)
No Conflicts.