Age | Commit message (Collapse) | Author | Files | Lines |
|
A set of small fixes after discovery during DCM's end-to-end testing:
- properly detect that a cert hasn't been issued yet (don't crash)
- in Monitor, don't pass namespace when querying for CSRs
- fixed incorrect /kubeconfig file encoding from yaml to json
Issue-ID: MULTICLOUD-1143
Change-Id: Ie813e377070b0751f0bfdabac8da50e3288090de
Signed-off-by: Igor D.C <igor.duarte.cardoso@intel.com>
|
|
These changes allow the Monitor to also track CSR
(CertificateSigningResource) resources which will make
it possible to know when a certificate has been issued by
the K8s cluster signer. In turn, DCM will be able to read,
store and use that certificate to generate kubeconfigs.
Out-of-tree actions required:
- publish monitor's docker image built from this source
onto emcov2/monitor:latest
Issue-ID: MULTICLOUD-1143
Change-Id: I7facd27bbfe08891151bb3b6a9a19948435e24e4
Signed-off-by: Igor D.C <igor.duarte.cardoso@intel.com>
|
|
This patch enhances the status query API.
- The ResourceBundleState CRD is modified to just use the
k8s Pod structure instead of a customized struct.
- Status queries can either present results showing
the rsync status of the composite app and resources
or from information received from the cluster via
the ResourceBundleState CR
- Query parameters are provided to the API call to
customize the query and response
- Support for querying status of cluster network
intents is added
Issue-ID: MULTICLOUD-1042
Signed-off-by: Eric Multanen <eric.w.multanen@intel.com>
Change-Id: Icca4cdd901e2f2b446414fade256fc24d87594cd
|
|
Changed Rsync to use ordered install.
Changed to use cli-runtime instead of
go-client. Based on code from repo
https://github.com/johandry/klient
Issue-ID: MULTICLOUD-1005
Signed-off-by: Ritu Sood <ritu.sood@intel.com>
Change-Id: I4c2537cb74bd4d24a409cc1f0b7f9ee0875a4e39
|
|
This patch provides the basic framework for supporting
monitoring of composite application resources in clusters.
1. Updates to the monitor files for use with v2.
2. Invokes the Watcher process per cluster/app when the
app is instantiated.
3. Adds a ResourceBundleState CR resource to the cluster/app
so that monitor will be able to update status to it.
4. Watcher updates appropriate appcontext status object
when updates are made in clusters by monitor
5. Update appcontext library to define a status handle
and object at the app/cluster level
6. Labels resources with an appropriate tracking label
to coordinate with the ResourceBundleState CR
Issue-ID: MULTICLOUD-1042
Signed-off-by: Eric Multanen <eric.w.multanen@intel.com>
Change-Id: If007c1fd86ca7a65bb941d1776cfd2d3afed766b
|
|
This operator monitors the status of
resources like pods, services, deployments,
daemonsets, configmaps etc. and updates the
status in the CR accordingly.
Issue-ID: MULTICLOUD-1047
Signed-off-by: Srivahni Chivukula <srivahni.chivukula@intel.com>
Change-Id: I7d92584a44c8add2df69f2985140a55b460ac037
|
|
Update the package path to use the standard github.com
path instead of making it a local path.
This allows import from other go projects.
Issue-ID: MULTICLOUD-666
Change-Id: I90ee8eba021a84e31a3dc3ab48b9edf3731e91a4
Signed-off-by: Kiran Kamineni <kiran.k.kamineni@intel.com>
|
|
Adding generated informers for CRD
These informers will be needed when we want to
watch these CRDs from the ONAP cluster
Generated using generate-groups.sh
from the kubernetes/code-generator repo
Issue-ID: MULTICLOUD-675
Change-Id: Ib7547666efa389534f0501f8dbab14c284dd76a6
Signed-off-by: Kiran Kamineni <kiran.k.kamineni@intel.com>
|
|
Adding generated listers for CRD
Generated using generate-groups.sh
from the kubernetes/code-generator repo
Issue-ID: MULTICLOUD-675
Change-Id: I6c68a9e98d96ed77b9e5fb78cb2458f9c0f4d55d
Signed-off-by: Kiran Kamineni <kiran.k.kamineni@intel.com>
|
|
Adding a typed client for CRD
Generated using the generate-groups.sh script from
the kubernetes/code-generator repo
Issue-ID: MULTICLOUD-675
Change-Id: I6c712980595dfed7a8b9c51f50edfc6788372dfd
Signed-off-by: Kiran Kamineni <kiran.k.kamineni@intel.com>
|
|
Add an operator to monitor resources at the edge location.
The operator listens to pods and services right now and stores
their information in a CustomResource
Issue-ID: MULTICLOUD-675
Change-Id: I801478a77fcd019010ea1b4388d6077f63b89d05
Signed-off-by: Kiran Kamineni <kiran.k.kamineni@intel.com>
|