hc-oam-controller is an Open Application Model (OAM) implementation based on oam-dev/oam-go-sdk for Kubernetes in HarmonyCloud.
The workload type (workloadType) is a field in the ComponentSchematic used by the developer to direct the runtime to properly execute the given component.
OAM have two kinds of workload types.
- Core workload types
- Extended workload types
Hc-oam-controller supports all of the Open Application Model Core Workload Types:
| Name | Type | Service endpoint | Replicable | Daemonized |
|---|---|---|---|---|
| Server | core.oam.dev/v1alpha1.Server | Yes | Yes | Yes |
| Singleton Server | core.oam.dev/v1alpha1.SingletonServer | Yes | No | Yes |
| Task | core.oam.dev/v1alpha1.Task | No | Yes | No |
| Singleton Task | core.oam.dev/v1alpha1.SingletonTask | No | No | No |
| Worker | core.oam.dev/v1alpha1.Worker | No | Yes | Yes |
| Singleton Worker | core.oam.dev/v1alpha1.SingletonWorker | No | No | Yes |
Currently, hc-oam-controller supports one extended workload:
A trait represents a piece of add-on functionality that attaches to a component instance. Traits augment components with additional operational features such as traffic routing rules (including load balancing policy, network ingress routing, circuit breaking, rate limiting), auto-scaling policies, upgrade strategies, and more. As such, traits represent features of the system that are operational concerns, as opposed to developer concerns.
Currently, hc-oam-controller supports the following traits:
Hc-oam-controller can be installed through helm v3 or kubetl.
$ kubectl create namespace oam-system
namespace/oam-system created
$ helm -n oam-system install --generate-name charts/hc-oam-controller
NAME: hc-oam-controller-1584418055
LAST DEPLOYED: Tue Mar 17 12:07:37 2020
NAMESPACE: oam-system
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
hc-oam-controller is an Open Application Model (OAM) implementation based on oam-dev/oam-go-sdk for Kubernetes in HarmonyCloud.
$
$ helm -n oam-system list
NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
hc-oam-controller-1584418055 oam-system 1 2020-03-17 12:07:37.437598 +0800 CST deployed hc-oam-controller-0.1.0 v0.1
$ kubectl -n oam-system get deploy,pod
NAME READY UP-TO-DATE AVAILABLE AGE
deployment.apps/hc-oam-controller-1584418055 1/1 1 1 26s
NAME READY STATUS RESTARTS AGE
pod/hc-oam-controller-1584418055-79bcdb6fc-k7trm 1/1 Running 0 26s
$ $ kubectl apply -f config/oam/crds/
customresourcedefinition.apiextensions.k8s.io/applicationconfigurations.core.oam.dev created
customresourcedefinition.apiextensions.k8s.io/applicationscopes.core.oam.dev created
customresourcedefinition.apiextensions.k8s.io/componentschematics.core.oam.dev created
customresourcedefinition.apiextensions.k8s.io/traits.core.oam.dev created
customresourcedefinition.apiextensions.k8s.io/workloadtypes.core.oam.dev created
$ kubectl apply -f config/hc-oam-controller/
namespace/oam-system created
deployment.apps/hc-oam-controller created
clusterrole.rbac.authorization.k8s.io/hc-oam-controller-role created
clusterrolebinding.rbac.authorization.k8s.io/hc-oam-controller-rolebinding created
$ kubectl create -f config/hc-oam-controller/traits
trait.core.oam.dev/auto-scaler created
trait.core.oam.dev/better-auto-scaler created
trait.core.oam.dev/ingress created
trait.core.oam.dev/log-pilot created
trait.core.oam.dev/manual-scaler created
trait.core.oam.dev/volume-mounter created
$ kubectl create -f config/hc-oam-controller/workloads
workloadtype.core.oam.dev/mysql-cluster created
$ kubectl -n oam-system get pod
NAME READY STATUS RESTARTS AGE
hc-oam-controller-666457bc6f-hsthf 1/1 Running 0 3mThis is a simple example of how to use the hc-oam-controller.
$ kubectl apply -f examples/samples/simple-example
applicationconfiguration.core.oam.dev/simple-app created
componentschematic.core.oam.dev/stateless-component created
$
$ kubectl get deploy,svc,pod
NAME READY UP-TO-DATE AVAILABLE AGE
deployment.extensions/demo 2/2 2 2 48s
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/demo ClusterIP 10.245.101.21 <none> 80/TCP 48s
NAME READY STATUS RESTARTS AGE
pod/demo-575577d55f-48lz6 1/1 Running 0 48s
pod/demo-575577d55f-5p5dc 1/1 Running 0 48s
$
$ kubectl delete -f examples/samples/simple-example
applicationconfiguration.core.oam.dev "simple-app" deleted
componentschematic.core.oam.dev "stateless-component" deleted
$ kubectl get deploy,pod,svc
No resources found.There are more examples in examples/.