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

vdk-pipeline-control-service: upgrade java client k8s version #1216

Merged
merged 4 commits into from
Oct 5, 2022

Conversation

murphp15
Copy link
Collaborator

@murphp15 murphp15 commented Oct 5, 2022

Why?

I upgraded java client k8s version when trying to fix an issue related to connecting to the k8s cluster.
This was ultimately not the fix that was needed. But considering the work is done I think it make sense to merge it regardless.

What?

Upgrade the version in gradle and make a few small code changes to support the new apis.

How has this been tested?

Unit tests, integration tests but no new tests have been added

What type of change are you making?

Upgrade the version in gradle and make a few small code changes to support the new apis.

Signed-off-by: murphp15 murphp15@tcd.ie

murphp15 and others added 2 commits October 5, 2022 11:18
Signed-off-by: murphp15 <murphp15@tcd.ie>
… flaxey tests.

Signed-off-by: murphp15 <murphp15@tcd.ie>
@murphp15 murphp15 changed the title vdk-pipeline-core: upgrade java client k8s version vdk-pipeline-control-service: upgrade java client k8s version Oct 5, 2022
@murphp15 murphp15 enabled auto-merge (squash) October 5, 2022 13:44
@murphp15 murphp15 merged commit 44c38bd into main Oct 5, 2022
@murphp15 murphp15 deleted the person/murphp15/update_k8s_version branch October 5, 2022 14:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants