[JBoss JIRA] (ISPN-10617) Operator Docs: Getting started with k8s/OpenShift
by Donald Naro (Jira)
[ https://issues.jboss.org/browse/ISPN-10617?page=com.atlassian.jira.plugin... ]
Donald Naro updated ISPN-10617:
-------------------------------
Sprint: DataGrid Sprint #36 (was: DataGrid Sprint #35)
> Operator Docs: Getting started with k8s/OpenShift
> -------------------------------------------------
>
> Key: ISPN-10617
> URL: https://issues.jboss.org/browse/ISPN-10617
> Project: Infinispan
> Issue Type: Task
> Components: Documentation-Servers
> Reporter: Donald Naro
> Assignee: Donald Naro
> Priority: Major
>
> assembly with getting started that includes procedure to setup pull request tokens. this should be done when engineering starts the work to create the cache service and dg service via the operator as well as the different profiles.
> clarify details about creating the operator. requires kubeadmin to install the operator into specific namespaces.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (ISPN-10617) Operator Docs: Getting started with k8s/OpenShift
by Donald Naro (Jira)
[ https://issues.jboss.org/browse/ISPN-10617?page=com.atlassian.jira.plugin... ]
Donald Naro updated ISPN-10617:
-------------------------------
Description:
assembly with getting started that includes procedure to setup pull request tokens. this should be done when engineering starts the work to create the cache service and dg service via the operator as well as the different profiles.
clarify details about creating the operator. requires kubeadmin to install the operator into specific namespaces.
was:assembly with getting started that includes procedure to setup pull request tokens
> Operator Docs: Getting started with k8s/OpenShift
> -------------------------------------------------
>
> Key: ISPN-10617
> URL: https://issues.jboss.org/browse/ISPN-10617
> Project: Infinispan
> Issue Type: Task
> Components: Documentation-Servers
> Reporter: Donald Naro
> Assignee: Donald Naro
> Priority: Major
>
> assembly with getting started that includes procedure to setup pull request tokens. this should be done when engineering starts the work to create the cache service and dg service via the operator as well as the different profiles.
> clarify details about creating the operator. requires kubeadmin to install the operator into specific namespaces.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (ISPN-10733) Operator Docs: Spec updates
by Donald Naro (Jira)
[ https://issues.jboss.org/browse/ISPN-10733?page=com.atlassian.jira.plugin... ]
Donald Naro updated ISPN-10733:
-------------------------------
Description:
https://github.com/infinispan/infinispan-operator/issues/169
Vittorio's comment in the issue. There are two main use cases:
Change that reflects to a statefulset.spec.containers field. This automatically triggers a redeploy. i.e. spec.container fields. - This doesn't need documentation because it's assumed that if you change the statefulset, the Operator redeploys the pods.
Change to other field or resource. In this case it would be good to have a list of 'redeployIfChanged' objects and check against it if a redeploy is needed or not. - Possibly need to document the list of objects.
was:https://github.com/infinispan/infinispan-operator/issues/169
> Operator Docs: Spec updates
> ---------------------------
>
> Key: ISPN-10733
> URL: https://issues.jboss.org/browse/ISPN-10733
> Project: Infinispan
> Issue Type: Task
> Components: Documentation-Servers
> Reporter: Donald Naro
> Assignee: Donald Naro
> Priority: Major
>
> https://github.com/infinispan/infinispan-operator/issues/169
> Vittorio's comment in the issue. There are two main use cases:
> Change that reflects to a statefulset.spec.containers field. This automatically triggers a redeploy. i.e. spec.container fields. - This doesn't need documentation because it's assumed that if you change the statefulset, the Operator redeploys the pods.
> Change to other field or resource. In this case it would be good to have a list of 'redeployIfChanged' objects and check against it if a redeploy is needed or not. - Possibly need to document the list of objects.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (ISPN-10733) Operator Docs: Spec updates
by Donald Naro (Jira)
[ https://issues.jboss.org/browse/ISPN-10733?page=com.atlassian.jira.plugin... ]
Donald Naro updated ISPN-10733:
-------------------------------
Sprint: DataGrid Sprint #36 (was: DataGrid Sprint #35)
> Operator Docs: Spec updates
> ---------------------------
>
> Key: ISPN-10733
> URL: https://issues.jboss.org/browse/ISPN-10733
> Project: Infinispan
> Issue Type: Task
> Components: Documentation-Servers
> Reporter: Donald Naro
> Assignee: Donald Naro
> Priority: Major
>
> https://github.com/infinispan/infinispan-operator/issues/169
> Vittorio's comment in the issue. There are two main use cases:
> Change that reflects to a statefulset.spec.containers field. This automatically triggers a redeploy. i.e. spec.container fields. - This doesn't need documentation because it's assumed that if you change the statefulset, the Operator redeploys the pods.
> Change to other field or resource. In this case it would be good to have a list of 'redeployIfChanged' objects and check against it if a redeploy is needed or not. - Possibly need to document the list of objects.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months