-
Notifications
You must be signed in to change notification settings - Fork 522
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
Namespace as resource fragment results in NullPointerException #511
Comments
12 tasks
Relates to #146 |
rohanKanojia
added a commit
to rohanKanojia/jkube
that referenced
this issue
Dec 10, 2020
…PointerException
rohanKanojia
added a commit
to rohanKanojia/jkube
that referenced
this issue
Dec 10, 2020
…PointerException + DefaultNamespaceEnricher should handle case when status is not provided in resource spec. + .metadata.namespace should be omitted from Project/Namespace resources since they are Cluster scoped + UndeployService should consider Project/Namespace resource while deletion phase
12 tasks
rohanKanojia
added a commit
to rohanKanojia/jkube
that referenced
this issue
Dec 23, 2020
…PointerException + DefaultNamespaceEnricher should handle case when status is not provided in resource spec. + .metadata.namespace should be omitted from Project/Namespace resources since they are Cluster scoped + UndeployService should consider Project/Namespace resource while deletion phase
rohanKanojia
added a commit
to rohanKanojia/jkube
that referenced
this issue
Jan 13, 2021
…PointerException + DefaultNamespaceEnricher should handle case when status is not provided in resource spec. + .metadata.namespace should be omitted from Project/Namespace resources since they are Cluster scoped + UndeployService should consider Project/Namespace resource while deletion phase
rohanKanojia
added a commit
to rohanKanojia/jkube
that referenced
this issue
Jan 15, 2021
…PointerException + DefaultNamespaceEnricher should handle case when status is not provided in resource spec. + .metadata.namespace should be omitted from Project/Namespace resources since they are Cluster scoped + UndeployService should consider Project/Namespace resource while deletion phase
manusa
pushed a commit
that referenced
this issue
Jan 18, 2021
+ DefaultNamespaceEnricher should handle case when status is not provided in resource spec. + .metadata.namespace should be omitted from Project/Namespace resources since they are Cluster scoped + UndeployService should consider Project/Namespace resource while deletion phase
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
We have DefaultNamespaceEnricher which seems to be taking care of creating a namespace on the fly when provided as a resource fragment. However, when I add a simple
Namespace
resource fragment insrc/main/jkube
like this:It results in
NullPointerException
:Info
mvn -v
) :Kubernetes / Red Hat OpenShift setup and version : Kubernetes 1.19.4
If it's a bug, how to reproduce : Just add namespace fragment and issue
mvn k8s:resource
If it's a feature request, what is your use case :
Sample Reproducer Project : https://github.com/r0haaaan/eclipse-jkube-sample-with-resource-fragments/tree/namespace-fragment
The text was updated successfully, but these errors were encountered: