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

Report "status" of TransportServer CRD #1659

Closed
chen23 opened this issue Jan 25, 2021 · 3 comments · Fixed by #2118
Closed

Report "status" of TransportServer CRD #1659

chen23 opened this issue Jan 25, 2021 · 3 comments · Fixed by #2118

Comments

@chen23
Copy link
Contributor

chen23 commented Jan 25, 2021

Title

Report "status" of TransportServer CRD

Description

Currently an end-user cannot tell whether the controller has pushed an update to the BIG-IP device. Ideally the status should report a timestamp that matches the last pushed update. Otherwise it is unclear whether a change has been applied or not.

Actual Problem

From an end-user it is not possible to tell whether a TransportServer has been pushed to a BIG-IP (or whether any errors). This would provide feedback if there is an issue (controller not running and/or BIG-IP unresponsive).

Solution Proposed

Add a Status that can be outputted when running "kubectl get ts -o wide" i.e.

NAME              VIRTUALSERVERADDRESS   VIRTUALSERVERPORT   POOL          POOLPORT   AGE  STATUS LASTUPDATE
my-frontend-crd   10.1.10.82             8080                my-frontend   80         10h  OK     3M

Alternatives

Currently you have to have privileges to look at the logs of the controller to check on status

Additional context

It is not possible to tell the state of a change whether successful or not.

@mdditt2000 mdditt2000 removed the untriaged no JIRA created label Mar 5, 2021
@mdditt2000 mdditt2000 added this to the 2.3 milestone Mar 5, 2021
@mdditt2000
Copy link
Contributor

Only the STATUS is still required. @trinaths @mdditt2000 please file JIRA for upcoming sprint.

@trinaths
Copy link
Contributor

trinaths commented Mar 9, 2021

Created CONTCNTR-2537 for internal tracking.

@mdditt2000 mdditt2000 modified the milestones: 2.3, 2.4.1 Mar 26, 2021
@mdditt2000
Copy link
Contributor

Currently targeted at 2.7

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