Functional test for Kubernetes load balancer
The blueprint for the Kubernetes external load balancer calls for a functional test to ensure functionality.
In the current implementation, a manual step is required to enter the user credential in the Kubernetes configuration.
As a result, the functional test is blocked at this time.
A blueprint has been registered to remove this limitation in the Mitaka release:
https:/
When this bug is resolved, the functional test can be added.
Blueprint information
- Status:
- Not started
- Approver:
- Spyros Trigazis
- Priority:
- Low
- Drafter:
- Ton Ngo
- Direction:
- Approved
- Assignee:
- Feilong Wang
- Definition:
- New
- Series goal:
- Accepted for rocky
- Implementation:
-
Not started
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
--
strigazi @ Sun Mar 25 16:42:01 UTC 2018
The cloud provider is in a working state, we can simply add a test for it here:
http://
--
A suggestion for the functional test is to follow the nginx example in the document for the load balancer:
https:/
The test would create a pod running nginx, then a service for this pod.
The service would indicate a load balancer is to be created.
Then the test would find the lb-vip created and query the endpoint for nginx.
The welcome message for nginx should be returned.
10/29/15
Per discussion at the Design Summit, new functional test should use Tempest.
Work Items
Dependency tree
* Blueprints in grey have been implemented.
