karmada-operator: add init workflow

[calvin0327]

Signed-off-by: calvin [email protected]

What type of PR is this?
/kind feature

What this PR does / why we need it:

Which issue(s) this PR fixes:
Part of Fixes #2979

Special notes for your reviewer:
Used workflow to install karmada. We divided the whole installation process into:
PrepareCrds => GenerateCert=> CreateNamespace => UploadKubeconfig => UploadCerts
=> Install Etcd => Apiserver => apply crds => install Component => install module => WaitControlPlane

Does this PR introduce a user-facing change?:

NONE

[calvin0327]

@lonelyCZ @carlory Do you have any comments on this approach? If there is no comment, I will continue.

[RainbowMango]

Hi @calvin0327 I can't figure out the process now. According to #2979, seems all tasks are now in WIP state.

[calvin0327]

Hi @calvin0327 I can't figure out the process now. According to #2979, seems all tasks are now in WIP state.

I have discussed with @carlory, and we will install karmada using the latest design, if the community thinks it is ok,
then we will close the previous pr: #2990

[lonelyCZ]

The process is same as karmadactl init, I think it is ok for the first version of operator.

[calvin0327]

😄，we will go on.

[calvin0327]

Here are the test result：

• deploy a karmada operator:

first, we need create secret of install cluster kubeconfig used by karmada operator, and create karmada operator deployment:

kubectl create secret generic my-kubeconfig --from-file=/Users/chenwen/.kube/config -n karmada-system
kubectl apply -f operator/config/deploy/karmada-operator.yaml

• create karmada cr:

kubectl apply -f operator/config/samples/karmada.yaml

apiVersion: operator.karmada.io/v1alpha1
kind: Karmada
metadata:
  namespace: test
  name: karmada-demo

• Observe the result:

[RainbowMango]

No worries, please tell us how to run it.

[calvin0327]

#3102 (comment)

There are demo steps above, I would like to explain if there is anything unclear here.

[lonelyCZ]

I just tested it in my env that worked fine. It was cool!!

[root@master67 config]# kubectl get pod -A
NAMESPACE        NAME                                                    READY   STATUS    RESTARTS   AGE
karmada-system   karmada-demo-aggregated-apiserver-575df97794-lsk75      1/1     Running   2          47m
karmada-system   karmada-demo-apiserver-6d8fbf4766-z68k9                 1/1     Running   0          47m
karmada-system   karmada-demo-controller-manager-5b86f67954-8t974        1/1     Running   0          47m
karmada-system   karmada-demo-etcd-0                                     1/1     Running   0          47m
karmada-system   karmada-demo-kube-controller-manager-747b44bff6-k4dl5   1/1     Running   0          47m
karmada-system   karmada-demo-scheduler-c8fd7f499-t5nt2                  1/1     Running   0          47m
karmada-system   karmada-demo-webhook-d8c5bb46d-kxkb2                    1/1     Running   0          47m
karmada-system   karmada-operator-845d586cd7-dbks7                       1/1     Running   0          57m

There are some suggestions for the moment, I will continue to review it.

[Poor12]

Some suggestions.

[calvin0327]

@Poor12 @lonelyCZ any other comments here?

[Poor12]

/assign
I will test and review ASAP.

[lonelyCZ]

LGTM, it has achieved a basic init worklow, we can optimize it in the feature.

cc @RainbowMango @Poor12

[Poor12]

/lgtm
It's time to move forward. Thanks @calvin0327 @lonelyCZ

[RainbowMango]

/approve

[karmada-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: RainbowMango

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [RainbowMango]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment