Skip to content
This repository has been archived by the owner on May 10, 2023. It is now read-only.

Kubernetes Operator - resolve protocol missing on hostname #14

Closed
Jimbo4794 opened this issue Mar 15, 2022 · 3 comments
Closed

Kubernetes Operator - resolve protocol missing on hostname #14

Jimbo4794 opened this issue Mar 15, 2022 · 3 comments
Assignees
@Jimbo4794

Comments

@Jimbo4794
Copy link
Contributor

Several components require a protocol inside the opterator which it bases from the k8s hostname. Need to add check and fill in missing protocol on those components
@Jimbo4794 Jimbo4794 self-assigned this Mar 15, 2022
@techcobweb
Copy link

@Jimbo4794 How do yo mean a protocol ? Do you have any examples of what's needed and where ?

@techcobweb techcobweb transferred this issue from galasa-dev/projectmanagement Nov 22, 2022
@techcobweb
Copy link

techcobweb commented Nov 23, 2022 •
edited
Loading

Given our recent decision to not persue the kube operator in its' current form, can this issue be closed @Jimbo4794 ?

@techcobweb
Copy link

Assuming we can close this. Please re-open if required.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@Jimbo4794 Jimbo4794

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@techcobweb @Jimbo4794