Roadmap : A list of prioritised issues.

[piyush-garg]

A list of prioritised for FKC. These issues are part of the backlog and we are prioritising in our following sprints:

Feature

• Implement waiUntilCondition Implement waitUntilCondition #989
• Kubernetes/Openshift mock server should be able to take customized config for client Kubernetes/Openshift mock server should be able to take customized config for client #998
• Provide equivalent of oc new-app Provide equivalent of oc new-app #929
• Template does not support ${{ }} Template doesn't support ${{ }} #959
• Create ISTIO Route Rule [Question] Create Istio RouteRule #942
• Add support for service catalog Add support for service catalog feature #973

Kubernetes and OpenShift Compatibility

• API version support for openshift API version support for OpenShift #919
• Kubernetes/Openshift version compatibility kubernetes version compatability #946
• [upgrade] Support for Kubernetes/Openshift v1.9/v3.9 [upgrade] support for Kubernetes/Openshift v1.9/v3.9 #1020

Test

• Add support for log() and exec() Add Support for log() and exec() tests in PodIT #975

Security

Documentation

• Add contributor guidelines Add contributor guideliness #980
• Add a doc that lists projects using the client Add a section in the doc that lists projects using the client #935

Uncategorised (Bug Fixes )

• Kubernetes Connection is not closed Kubernetes Connection is not closed. #1013
• waitUntilReady does not work for big timeouts waitUntilReady does not work for big timeouts #917
• Not able to trigger build via WebhookTriggerbuild Not able to trigger build via WebHookTriggerBuilder #986
• Failure in update while on CRUD mode Failure in update while operating on CRUD mode on Kubernetes mock server #957
• Add Location Header while deleting a project Add Location header when deleting a project #1006
• Multiple document handling breaks Multiple document handling breaks if --- found anywhere in the document. #1004
• Loading a template is breaking Loading a template from file and processing it locally by passing a parameters map is broken #1005
• Close is not closing the connection immediately Close() doesn't immediately close the connection #960
• Unable to update stateful set if spec contains an empty array Unable to update StatefulSet if spec contains an empty "array" property #931
• Fluent Object does not contain Additional Properties mao Fluent object not container AdditionalProperties map #993
• Use exec, copy file to pod is too slow use exec copy file to pod too slow #1008
• DSL execute too slow use exec copy file to pod too slow #1008
• Create Cron Job How to create a CronJob? #920

This list is just a first stab at handling and reducing the backlog that we have accumulated in the fabric8-kubernetes-client issues list. Please comment on this issue and let us know if you feel there are issues that we might have overlooked or need to be prioritized.

[maitredede]

Hi,
I would be pleased to have cronjobs api avaible :)

[brentpearson]

+1 for cronjobs!

[skonto]

Could you also add (unless it already exists) a method to wait on some result/condition from a command executed against a pod (I was looking for this here apache/spark#21652 (comment)).
Timeouts like here: https://github.com/fabric8io/kubernetes-client/blob/master/kubernetes-examples/src/main/java/io/fabric8/kubernetes/examples/ExecPipesExample.java#L60
look a bit arbitrary.

[rohanKanojia]

@skonto Do you think #989 matches your usecase? It's in our plan for implementation

[skonto]

@rohanKanojia I will have a look, using a terminal with a container is my use case.

[stale]

This issue has been automatically marked as stale because it has not had any activity since 90 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions!

[stale]

This issue has been automatically marked as stale because it has not had any activity since 90 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions!

[stale]

This issue has been automatically marked as stale because it has not had any activity since 90 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions!

[stale]

This issue has been automatically marked as stale because it has not had any activity since 90 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions!

[stale]

This issue has been automatically marked as stale because it has not had any activity since 90 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions!