karmada/hack
karmada-bot ba0d7dc786
Merge pull request #1676 from XiShanYongYe-Chang/install-metallb
Creating Loadbalancer Type Service by Installing the Metallb
2022-05-07 10:27:25 +08:00
..
boilerplate add codegen scripts 2020-11-11 10:22:54 +08:00
tools upgrade ginkgo to v2 2022-04-12 20:39:29 +08:00
.import-aliases update discoveryv1beta1 to discoveryv1 for endpointslice 2021-12-18 17:19:21 +08:00
OWNERS Add hack owners 2021-06-08 11:01:32 +08:00
README.md Merge pull request #1146 from leonharetd/master 2021-12-30 19:19:44 +08:00
cherry_pick_pull.sh Orgnize documents about cherry-picks 2022-01-10 11:11:31 +08:00
create-cluster.sh Update kind from v0.11.2 to v0.12.0 2022-03-15 21:01:06 +08:00
delete-cluster.sh optimize installation 2021-05-28 00:34:55 +08:00
deploy-agent-and-estimator.sh repair question template and comment of the script 2021-10-07 15:26:37 +08:00
deploy-karmada-agent.sh Implement karmadactl get to support pull mode cluster 2022-04-02 14:46:30 +08:00
deploy-karmada.sh Creating Loadbalancer Type Service by Installing the Metallb 2022-04-27 15:37:37 +08:00
deploy-scheduler-estimator.sh deploy scheduler estimator when local up karmada 2021-09-27 20:53:46 +08:00
docker.sh code optimization : use make instead of go build on docker build stage 2022-05-05 20:48:37 +08:00
local-up-karmada.sh add timezone 2022-04-28 22:11:04 +08:00
post-run-e2e.sh Creating Loadbalancer Type Service by Installing the Metallb 2022-04-27 15:37:37 +08:00
pre-run-e2e.sh Creating Loadbalancer Type Service by Installing the Metallb 2022-04-27 15:37:37 +08:00
remote-up-karmada.sh Add Karmada logo in remote-up-karmada.sh 2022-03-01 09:50:36 +08:00
run-e2e.sh Set e2e to run in parallel 2022-04-15 11:47:26 +08:00
undeploy-karmada.sh clear global resources while undeploy cluster 2022-05-04 13:54:27 +08:00
update-all.sh Add verify script for swagger-docs 2022-03-21 16:56:08 +08:00
update-codegen.sh Update generated openapi 2022-03-04 14:23:14 +08:00
update-crdgen.sh add MultiClusterIngress API for MCI feature 2022-02-21 09:40:55 +08:00
update-estimator-protobuf.sh add mock client 2022-01-22 22:00:04 +08:00
update-import-aliases.sh Replace go get with go install 2021-11-25 10:34:49 +08:00
update-swagger-docs.sh Generate API documents for Karmada CRD 2022-03-08 19:52:05 +08:00
update-vendor.sh add go mod tidy to update vendor 2021-10-22 11:11:17 +08:00
util.sh refactor Dockerfile using multi-stage docker build 2022-04-27 10:45:49 +08:00
verify-all.sh Add verify script for swagger-docs 2022-03-21 16:56:08 +08:00
verify-codegen.sh change ci to self-hosted from ubuntu-latest (#225) 2021-03-20 21:14:01 +08:00
verify-crdgen.sh unify the crds used by helm chart and the installation scripts 2021-09-10 17:59:15 +08:00
verify-estimator-protobuf.sh add protobuf verification script 2021-11-23 16:50:52 +08:00
verify-import-aliases.sh Replace go get with go install 2021-11-25 10:34:49 +08:00
verify-staticcheck.sh Bump golangci-lint version to v1.42.1 2021-10-12 17:46:32 +08:00
verify-swagger-docs.sh Add verify script for swagger-docs 2022-03-21 16:56:08 +08:00
verify-vendor.sh add go mod tidy to update vendor 2021-10-22 11:11:17 +08:00
version.sh [fix] add execute permission to hack/version.sh 2022-05-01 13:57:22 +08:00

README.md

Karmada hack GuideLines

This document describes how you can use the scripts from the hack directory and gives a brief introduction and explanation of these scripts.

Scripts in this directory are mainly for the purpose which improves development efficiency and ensures development quality.

Key scripts

For end-user

  • local-up-karmada.sh This script will quickly set up a local development environment with member clusters based on the current codebase.

  • remote-up-karmada.sh This script will install Karmada to a standalone K8s cluster, this cluster may be real, remote , and even for production. It is worth noting for the connectivity from your client to Karmada API server, it will directly use host network by default, else export LOAD_BALANCER=true with the LoadBalancer type service before the following script. If your want to customize a load balancer service, you may add the annotations at the metadata part of service karmada-apiserver in ../artifacts/deploy/karmada-apiserver.yaml before the installing. The following is an example.

  # If you want to use a internal IP in public cloud you need to fill the following annotation, 
  # For the more annotation settings please read your public cloud docs
  annotations: 
    # Aliyun cloud
    #service.beta.kubernetes.io/alibaba-cloud-loadbalancer-address-type: "intranet"
    # Huawei cloud
    #kubernetes.io/elb.autocreate: '{"type":"inner"}'
    # Tencent cloud (you need to replace words 'xxxxxxxx')
    #service.kubernetes.io/qcloud-loadbalancer-internal-subnetid: subnet-xxxxxxxx

The usage of remote-up-karmada.sh:

# hack/remote-up-karmada.sh <kubeconfig> <context_name>

kubeconfig is your cluster's kubeconfig that you want to install to

context_name is the name of context in 'kubeconfig'

  • deploy-karmada-agent.sh This script will install Karmada Agent to the specific cluster.

  • deploy-scheduler-estimator.sh This script will only install Karmada Scheduler Estimator to the specific cluster. Please follow the instruction for more details.

  • deploy-agent-and-estimator.sh This script will install Karmada Agent and Karmada Scheduler Estimator to the specific cluster together. If applied, there is no need to use the extra deploy-karmada-agent.sh and deploy-scheduler-estimator.sh script.

  • undeploy-karmada.sh This script will uninstall Karmada from the specific cluster. It will uninstall Karmada from your local environment default. If you installed Karmada with remote-up-karmada.sh, please use it like this: hack/undeploy-karmada.sh <KUBECONFIG> <CONTEXT_NAME>, the same parameters as you input at the installing step.

  • delete-cluster.sh This script delete a kube cluster by kind, please use it like this: hack/delete-cluster.sh.sh <CLUSTER_NAME> <KUBECONFIG>

For CI pipeline

  • local-up-karmada.sh This script also used for testing.

  • run-e2e.sh This script runs e2e test against on Karmada control plane. You should prepare your environment in advance with local-up-karmada.sh.

Some internal scripts

These scripts are not intended used by end-users, just for the development

  • deploy-karmada.sh Underlying common implementation for local-up-karmada.sh and remote-up-karmada.sh.

  • util.sh All util functions.