You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@submarine.apache.org by "Kai-Hsun Chen (Jira)" <ji...@apache.org> on 2021/06/18 15:00:00 UTC
[jira] [Resolved] (SUBMARINE-848) Make submarine CR and resources
created in the same namespace
[ https://issues.apache.org/jira/browse/SUBMARINE-848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kai-Hsun Chen resolved SUBMARINE-848.
-------------------------------------
Fix Version/s: 0.6.0
Target Version: 0.6.0
Resolution: Fixed
Issue resolved by pull request 606.
Link: https://github.com/apache/submarine/pull/606
> Make submarine CR and resources created in the same namespace
> -------------------------------------------------------------
>
> Key: SUBMARINE-848
> URL: https://issues.apache.org/jira/browse/SUBMARINE-848
> Project: Apache Submarine
> Issue Type: Sub-task
> Reporter: Chi-Sheng Liu
> Assignee: Chi-Sheng Liu
> Priority: Major
> Labels: pull-request-available
> Fix For: 0.6.0
>
>
> https://pkg.go.dev/k8s.io/apimachinery@v0.20.4/pkg/apis/meta/v1#OwnerReference
> The documentation above says that we should not create cross-namespace ownerReferences but our submarine CR and the resources created by operator are in different namespaces. After discussion with others, we decided to put them in the same namespace temporarily.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@submarine.apache.org
For additional commands, e-mail: dev-help@submarine.apache.org