Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(trait): never fallback to client-side apply unless server-side apply is incombatible #2421

Merged
merged 1 commit into from
Jun 22, 2021

Conversation

tadayosi
Copy link
Member

It's convenient for debugging if we output log with error why SSA failed at deployer trait (other than incompatibility) before attempting to CSA so that we can know the direct reason why the operation failed.

Release Note

NONE

pkg/trait/deployer.go Outdated Show resolved Hide resolved
@tadayosi tadayosi changed the title chore(trait): log error as info when failed with SSA for reason other than compatibility fix(trait): never fallback to client-side apply unless server-side apply is incombatible Jun 21, 2021
@astefanutti
Copy link
Member

That fails on OpenShift 3. It seems the current isIncompatibleServerError method does not work to report SSA is not supported.

…ply is incombatible

CSA support is mainly kept for compatibility reason and will ultimately be
removed, so it should only be used as fallback when SSA is known to be
unavailable.
@astefanutti astefanutti merged commit 7ac2aaa into apache:main Jun 22, 2021
@nicolaferraro nicolaferraro mentioned this pull request Jul 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants