diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 328e4a7a240..cbc48689c15 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -1,6 +1,6 @@ # Welcome -Welcome to Alkaid! +Welcome to Arktos! - [Before you get started](#before-you-get-started) - [Code of Conduct](#code-of-conduct) @@ -20,19 +20,19 @@ Welcome to Alkaid! ## Code of Conduct -Please make sure to read and observe our [Code of Conduct](https://github.com/futurewei-cloud/alkaid/blob/master/code-of-conduct.md). +Please make sure to read and observe our [Code of Conduct](https://github.com/futurewei-cloud/arktos/blob/master/code-of-conduct.md). # Getting started - Fork the repository on GitHub -- Visit [README](https://github.com/futurewei-cloud/alkaid#build-alkaid) for build instructions. +- Visit [README](https://github.com/futurewei-cloud/arktos#build-arktos) for build instructions. # Your First Contribution We will help you to contribute in different areas like filing issues, developing features, fixing critical bugs and getting your work reviewed and merged. -If you have questions about the development process, feel free to jump into our [slack channel](https://app.slack.com/client/TMNECBVT5/CRRUU7137) or join our [email group](https://groups.google.com/forum/#!forum/alkaid-user). +If you have questions about the development process, feel free to jump into our [slack channel](https://app.slack.com/client/TMNECBVT5/CRRUU7137) or join our [email group](https://groups.google.com/forum/#!forum/arktos-user). ## Find something to work on @@ -42,9 +42,9 @@ Here is how you get started. ### Find a good first topic -There are multiple repositories ([Alkaid](https://github.com/futurewei-cloud/alkaid), [Alkaid-vm-runtime](https://github.com/futurewei-cloud/alkaid-vm-runtime), [Alkaid-cniplugins](https://github.com/futurewei-cloud/alkaid-cniplugins)) within the Alkaid organization. +There are multiple repositories ([Arktos](https://github.com/futurewei-cloud/arktos), [Arktos-vm-runtime](https://github.com/futurewei-cloud/arktos-vm-runtime), [Arktos-cniplugins](https://github.com/futurewei-cloud/arktos-cniplugins)) within the Arktos organization. Each repository has beginner-friendly issues that provide a good starting point. -For example, [Alkaid](https://github.com/futurewei-cloud/alkaid) has [help wanted](https://github.com/futurewei-cloud/alkaid/labels/help%20wanted) and [good first issue](https://github.com/futurewei-cloud/alkaid/labels/good%20first%20issue) labels for issues that should not need deep knowledge of the system. We can help new contributors who wish to work on such issues. +For example, [Arktos](https://github.com/futurewei-cloud/arktos) has [help wanted](https://github.com/futurewei-cloud/arktos/labels/help%20wanted) and [good first issue](https://github.com/futurewei-cloud/arktos/labels/good%20first%20issue) labels for issues that should not need deep knowledge of the system. We can help new contributors who wish to work on such issues. ### Work on an issue @@ -55,9 +55,9 @@ then the robot will assign the issue to you and your name will present at `Assig ### File an Issue While we encourage everyone to contribute code, it is also appreciated when someone reports an issue. -Issues should be filed under the appropriate Alkaid sub-repository. +Issues should be filed under the appropriate Arktos sub-repository. -*Example:* An Alkaid issue should be opened to [Alkaid](https://github.com/futurewei-cloud/alkaid). And the same should apply to [Alkaid-vm-runtime](https://github.com/futurewei-cloud/alkaid-vm-runtime) and [Alkaid-cniplugins](https://github.com/futurewei-cloud/alkaid-cniplugins). +*Example:* An Arktos issue should be opened to [Arktos](https://github.com/futurewei-cloud/arktos). And the same should apply to [Arktos-vm-runtime](https://github.com/futurewei-cloud/arktos-vm-runtime) and [Arktos-cniplugins](https://github.com/futurewei-cloud/arktos-cniplugins). Please follow the prompted submission guidelines while opening an issue. @@ -71,13 +71,13 @@ This is a rough outline of what a contributor's workflow looks like: - Make commits of logical units. - Make sure commit messages are in the proper format (see below). - Push changes in a topic branch to a personal fork of the repository. -- Submit a pull request to [Alkaid](https://github.com/futurewei-cloud/alkaid). +- Submit a pull request to [Arktos](https://github.com/futurewei-cloud/arktos). - The PR must receive an approval from two team members including at least one maintainer. ## Creating Pull Requests Pull requests are often called simply "PR". -Alkaid generally follows the standard [github pull request](https://help.github.com/articles/about-pull-requests/) process. +Arktos generally follows the standard [github pull request](https://help.github.com/articles/about-pull-requests/) process. To submit a proposed change, please develop the code/fix and add new test cases. After that, run these local verifications before submitting pull request to predict the pass or fail of continuous integration. @@ -125,17 +125,17 @@ There are multiple types of tests. The location of the test code varies with type, as do the specifics of the environment needed to successfully run the test: * Unit: These confirm that a particular function behaves as intended. Unit test source code can be found adjacent to the corresponding source code within a given package. These are easily run locally by any developer. -* Integration: These tests cover interactions of package components or interactions between Alkaid components. +* Integration: These tests cover interactions of package components or interactions between Arktos components. * End-to-end ("e2e"): These are broad tests of overall system behavior and coherence. Continuous integration will run these tests on PRs. ## Documents and Support -The [design document folder](https://github.com/futurewei-cloud/alkaid/tree/master/docs/design-proposals) contains the detailed design of already implemented features, and also some thoughts for planned features. +The [design document folder](https://github.com/futurewei-cloud/arktos/tree/master/docs/design-proposals) contains the detailed design of already implemented features, and also some thoughts for planned features. -The [user guide folder](https://github.com/futurewei-cloud/alkaid/tree/master/docs/user-guide) provides information about these features from users' perspective. +The [user guide folder](https://github.com/futurewei-cloud/arktos/tree/master/docs/user-guide) provides information about these features from users' perspective. -To report a problem, please [create an issue](https://github.com/futurewei-cloud/alkaid/issues) in the project repo. +To report a problem, please [create an issue](https://github.com/futurewei-cloud/arktos/issues) in the project repo. -To ask a question, you can either chat with project members in the [slack channel](https://app.slack.com/client/TMNECBVT5/CRRUU7137), post in the [email group](https://groups.google.com/forum/#!forum/alkaid-user), or [create an issue](https://github.com/futurewei-cloud/alkaid/issues) of question type in the repo. +To ask a question, you can either chat with project members in the [slack channel](https://app.slack.com/client/TMNECBVT5/CRRUU7137), post in the [email group](https://groups.google.com/forum/#!forum/arktos-user), or [create an issue](https://github.com/futurewei-cloud/arktos/issues) of question type in the repo. diff --git a/README.md b/README.md index 15dd1dbb391..d1cbc4eee51 100644 --- a/README.md +++ b/README.md @@ -1,30 +1,30 @@ -# Alkaid +# Arktos
-## What Alkaid is +## What Arktos is -Alkaid is an open source cluster management system designed for large scale clouds. It is evolved from the open source [Kubernetes](https://github.com/kubernetes/kubernetesh) v1.15 codebase with some fundamental improvements. +Arktos is an open source cluster management system designed for large scale clouds. It is evolved from the open source [Kubernetes](https://github.com/kubernetes/kubernetesh) v1.15 codebase with some fundamental improvements. -Alkaid aims to be an open source solution to address key challenges of large scale clouds, including system scalability, resource efficiency, multitenancy, cross-AZ resiliency, and the native support for the fast-growing modern workloads such as containers and serverless functions. +Arktos aims to be an open source solution to address key challenges of large scale clouds, including system scalability, resource efficiency, multitenancy, cross-AZ resiliency, and the native support for the fast-growing modern workloads such as containers and serverless functions. ---- -## Key Features of Alkaid +## Key Features of Arktos ### Large Scalability -Alkaid achieves a scalable architecture by partitioning and replicating system components, including API Server, storage, controllers and data plane. The eventual goal of Alkaid is to support 100K nodes with a single cross-AZ control plane. +Arktos achieves a scalable architecture by partitioning and replicating system components, including API Server, storage, controllers and data plane. The eventual goal of Arktos is to support 100K nodes with a single cross-AZ control plane. ### Multitenancy -Alkaid implements a hard multi-tenancy model to meet the strict isolation requirement highly desired by a typical public cloud environment. Tenant is a built-in object in the system, and some flexible multi-tenancy models can also be supported with customized resource authorization rules. +Arktos implements a hard multi-tenancy model to meet the strict isolation requirement highly desired by a typical public cloud environment. Tenant is a built-in object in the system, and some flexible multi-tenancy models can also be supported with customized resource authorization rules. ### Native VM Support -In addition to container orchestration, Alkaid implements a built-in support for VMs. In Alkaid a pod can contain either containers or a VM. They are scheduled the same way and launched by node agent using different runtime servers. VMs and containers are both the first-class citizens in Alkaid. +In addition to container orchestration, Arktos implements a built-in support for VMs. In Arktos a pod can contain either containers or a VM. They are scheduled the same way and launched by node agent using different runtime servers. VMs and containers are both the first-class citizens in Arktos. ### More Planned Features @@ -32,34 +32,34 @@ In addition to container orchestration, Alkaid implements a built-in support for More features are planned but not started yet, including intelligent scheduling, in-place resource update, QoS enforcement, etc. -## Build Alkaid +## Build Arktos -To build Alkaid, you just need to clone the repo and run "make": +To build Arktos, you just need to clone the repo and run "make": ##### Note: you need to have a working [Go 1.12 environment](https://golang.org/doc/install). Go 1.13 is not supported yet. ``` mkdir -p $GOPATH/src/github.com cd $GOPATH/src/github.com -git clone https://github.com/futurewei-cloud/alkaid -cd alkaid +git clone https://github.com/futurewei-cloud/arktos +cd arktos make ``` -## Run Alkaid +## Run Arktos -To run a single-node Alkaid cluster in your local development box: +To run a single-node Arktos cluster in your local development box: ``` -cd $GOPATH/src/github.com/alkaid -hack/alkaid-up.sh +cd $GOPATH/src/github.com/arktos +hack/arktos-up.sh ``` -After the Alkaid cluster is up, you can access the cluster with [Kubectl](https://kubernetes.io/docs/tasks/tools/install-kubectl/) tool just like what you do with a Kubernetes cluster. For example: +After the Arktos cluster is up, you can access the cluster with [Kubectl](https://kubernetes.io/docs/tasks/tools/install-kubectl/) tool just like what you do with a Kubernetes cluster. For example: ``` -cd $GOPATH/src/github.com/alkaid +cd $GOPATH/src/github.com/arktos cluster/kubectl.sh get nodes ``` @@ -67,10 +67,10 @@ For more complicated cluster setups, an automated deployment tool is not availab ## Documents and Support -The [design document folder](https://github.com/futurewei-cloud/alkaid/tree/master/docs/design-proposals/) contains the detailed design of already implemented features, and also some thoughts for planned features. +The [design document folder](https://github.com/futurewei-cloud/arktos/tree/master/docs/design-proposals/) contains the detailed design of already implemented features, and also some thoughts for planned features. -The [user guide folder](https://github.com/futurewei-cloud/alkaid/tree/master/docs/user-guide/) provides information about these features from users' perspective. +The [user guide folder](https://github.com/futurewei-cloud/arktos/tree/master/docs/user-guide/) provides information about these features from users' perspective. -To report a problem, please [create an issue](https://github.com/futurewei-cloud/alkaid/issues) in the project repo. +To report a problem, please [create an issue](https://github.com/futurewei-cloud/arktos/issues) in the project repo. -To ask a question, you can either chat with project members in the [slack channels](http://alkaidworkspace.slack.com/), post in the [email group](https://groups.google.com/forum/#!forum/alkaid-user), or [create an issue](https://github.com/futurewei-cloud/alkaid/issues) of question type in the repo. +To ask a question, you can either chat with project members in the [slack channels](http://arktosworkspace.slack.com/), post in the [email group](https://groups.google.com/forum/#!forum/arktos-user), or [create an issue](https://github.com/futurewei-cloud/arktos/issues) of question type in the repo. diff --git a/SUPPORT.md b/SUPPORT.md index 12159e54a58..b0bfc387386 100644 --- a/SUPPORT.md +++ b/SUPPORT.md @@ -1,21 +1,21 @@ -## Support for deploying and using Alkaid +## Support for deploying and using Arktos -Welcome to Alkaid! We use GitHub for tracking bugs and feature requests. -This isn't the right place to get support for using Alkaid, but the following resources are available below, thanks for understanding. +Welcome to Arktos! We use GitHub for tracking bugs and feature requests. +This isn't the right place to get support for using Arktos, but the following resources are available below, thanks for understanding. ### Documentation -* [User Guide](https://github.com/futurewei-cloud/alkaid/tree/master/docs/user-guide/) -* [Design Documents](https://github.com/futurewei-cloud/alkaid/tree/master/docs/design-proposals/) +* [User Guide](https://github.com/futurewei-cloud/arktos/tree/master/docs/user-guide/) +* [Design Documents](https://github.com/futurewei-cloud/arktos/tree/master/docs/design-proposals/) ### Slack Channels -* [Slack](http://alkaidworkspace.slack.com/) : +* [Slack](http://arktosworkspace.slack.com/) : The `#developers` and `#users` channels are usual places where people offer support. ### Google Groups -* [Alkaid User](https://groups.google.com/forum/#!forum/alkaid-user/) -* [Alkaid Developer](https://groups.google.com/forum/#!forum/alkaid-dev/) \ No newline at end of file +* [Arktos User](https://groups.google.com/forum/#!forum/arktos-user/) +* [Arktos Developer](https://groups.google.com/forum/#!forum/arktos-dev/) \ No newline at end of file diff --git a/build/common.sh b/build/common.sh index 9df193ba0ef..c05a6be3f55 100755 --- a/build/common.sh +++ b/build/common.sh @@ -1,7 +1,7 @@ #!/usr/bin/env bash # Copyright 2014 The Kubernetes Authors. -# Copyright 2020 Authors of Alkaid - file modified. +# Copyright 2020 Authors of Arktos - file modified. # # Licensed under the Apache License, Version 2.0 (the "License"); # you may not use this file except in compliance with the License. diff --git a/build/debian-hyperkube-base/Dockerfile b/build/debian-hyperkube-base/Dockerfile index 098aea189c0..5f15f6d3b06 100644 --- a/build/debian-hyperkube-base/Dockerfile +++ b/build/debian-hyperkube-base/Dockerfile @@ -1,5 +1,5 @@ # Copyright 2017 The Kubernetes Authors. -# Copyright 2020 Authors of Alkaid - file modified. +# Copyright 2020 Authors of Arktos - file modified. # # Licensed under the Apache License, Version 2.0 (the "License"); # you may not use this file except in compliance with the License. diff --git a/build/lib/release.sh b/build/lib/release.sh index 83b7be3d7e9..d24082723be 100644 --- a/build/lib/release.sh +++ b/build/lib/release.sh @@ -1,7 +1,7 @@ #!/usr/bin/env bash # Copyright 2016 The Kubernetes Authors. -# Copyright 2020 Authors of Alkaid - file modified. +# Copyright 2020 Authors of Arktos - file modified. # # Licensed under the Apache License, Version 2.0 (the "License"); # you may not use this file except in compliance with the License. diff --git a/build/root/Makefile b/build/root/Makefile index e7b0746da78..283770f7310 100644 --- a/build/root/Makefile +++ b/build/root/Makefile @@ -1,5 +1,5 @@ # Copyright 2016 The Kubernetes Authors. -# Copyright 2020 Authors of Alkaid - file modified. +# Copyright 2020 Authors of Arktos - file modified. # # Licensed under the Apache License, Version 2.0 (the "License"); # you may not use this file except in compliance with the License. @@ -158,7 +158,7 @@ update: else update: generated_files CALLED_FROM_MAIN_MAKEFILE=1 hack/make-rules/update.sh - hack/alkaid_copyright.sh $(PWD) $(OUT_DIR) + hack/arktos_copyright.sh $(PWD) $(OUT_DIR) endif define CHECK_TEST_HELP_INFO diff --git a/build/run.sh b/build/run.sh index 10db88da25b..199a2c591a8 100755 --- a/build/run.sh +++ b/build/run.sh @@ -1,7 +1,7 @@ #!/usr/bin/env bash # Copyright 2014 The Kubernetes Authors. -# Copyright 2020 Authors of Alkaid - file modified. +# Copyright 2020 Authors of Arktos - file modified. # # Licensed under the Apache License, Version 2.0 (the "License"); # you may not use this file except in compliance with the License. @@ -43,4 +43,4 @@ if [[ ${KUBE_RUN_COPY_OUTPUT} =~ ^[yY]$ ]]; then kube::build::copy_output fi -${KUBE_ROOT}/hack/alkaid_copyright.sh ${KUBE_ROOT} ${KUBE_ROOT}/_output +${KUBE_ROOT}/hack/arktos_copyright.sh ${KUBE_ROOT} ${KUBE_ROOT}/_output diff --git a/cluster/gce/config-default.sh b/cluster/gce/config-default.sh index 8d6660ab11b..57f27b47678 100755 --- a/cluster/gce/config-default.sh +++ b/cluster/gce/config-default.sh @@ -1,7 +1,7 @@ #!/usr/bin/env bash # Copyright 2014 The Kubernetes Authors. -# Copyright 2020 Authors of Alkaid - file modified. +# Copyright 2020 Authors of Arktos - file modified. # # Licensed under the Apache License, Version 2.0 (the "License"); # you may not use this file except in compliance with the License. diff --git a/cluster/gce/config-test.sh b/cluster/gce/config-test.sh index 403e9e5ad52..611da85fa07 100755 --- a/cluster/gce/config-test.sh +++ b/cluster/gce/config-test.sh @@ -1,7 +1,7 @@ #!/usr/bin/env bash # Copyright 2014 The Kubernetes Authors. -# Copyright 2020 Authors of Alkaid - file modified. +# Copyright 2020 Authors of Arktos - file modified. # # Licensed under the Apache License, Version 2.0 (the "License"); # you may not use this file except in compliance with the License. diff --git a/cluster/gce/gci/configure-helper.sh b/cluster/gce/gci/configure-helper.sh index aaf85744590..b25f4f5b9bb 100644 --- a/cluster/gce/gci/configure-helper.sh +++ b/cluster/gce/gci/configure-helper.sh @@ -1,7 +1,7 @@ #!/usr/bin/env bash # Copyright 2016 The Kubernetes Authors. -# Copyright 2020 Authors of Alkaid - file modified. +# Copyright 2020 Authors of Arktos - file modified. # # Licensed under the Apache License, Version 2.0 (the "License"); # you may not use this file except in compliance with the License. diff --git a/cluster/gce/gci/configure.sh b/cluster/gce/gci/configure.sh index a19c7eb88ab..3a889525a3d 100644 --- a/cluster/gce/gci/configure.sh +++ b/cluster/gce/gci/configure.sh @@ -1,7 +1,7 @@ #!/usr/bin/env bash # Copyright 2016 The Kubernetes Authors. -# Copyright 2020 Authors of Alkaid - file modified. +# Copyright 2020 Authors of Arktos - file modified. # # Licensed under the Apache License, Version 2.0 (the "License"); # you may not use this file except in compliance with the License. diff --git a/cluster/gce/gci/master-helper.sh b/cluster/gce/gci/master-helper.sh index b15f2b1fdcb..a4ae7738e3f 100755 --- a/cluster/gce/gci/master-helper.sh +++ b/cluster/gce/gci/master-helper.sh @@ -1,7 +1,7 @@ #!/usr/bin/env bash # Copyright 2016 The Kubernetes Authors. -# Copyright 2020 Authors of Alkaid - file modified. +# Copyright 2020 Authors of Arktos - file modified. # # Licensed under the Apache License, Version 2.0 (the "License"); # you may not use this file except in compliance with the License. diff --git a/cluster/gce/util.sh b/cluster/gce/util.sh index 0fe0199258c..a540abb4d7a 100755 --- a/cluster/gce/util.sh +++ b/cluster/gce/util.sh @@ -1,7 +1,7 @@ #!/usr/bin/env bash # Copyright 2017 The Kubernetes Authors. -# Copyright 2020 Authors of Alkaid - file modified. +# Copyright 2020 Authors of Arktos - file modified. # # Licensed under the Apache License, Version 2.0 (the "License"); # you may not use this file except in compliance with the License. diff --git a/cluster/kubemark/gce/config-default.sh b/cluster/kubemark/gce/config-default.sh index 7faa567978c..cf078aef129 100644 --- a/cluster/kubemark/gce/config-default.sh +++ b/cluster/kubemark/gce/config-default.sh @@ -1,7 +1,7 @@ #!/usr/bin/env bash # Copyright 2017 The Kubernetes Authors. -# Copyright 2020 Authors of Alkaid - file modified. +# Copyright 2020 Authors of Arktos - file modified. # # Licensed under the Apache License, Version 2.0 (the "License"); # you may not use this file except in compliance with the License. diff --git a/cluster/validate-cluster.sh b/cluster/validate-cluster.sh index 69a23874812..b6801c76788 100755 --- a/cluster/validate-cluster.sh +++ b/cluster/validate-cluster.sh @@ -1,7 +1,7 @@ #!/usr/bin/env bash # Copyright 2014 The Kubernetes Authors. -# Copyright 2020 Authors of Alkaid - file modified. +# Copyright 2020 Authors of Arktos - file modified. # # Licensed under the Apache License, Version 2.0 (the "License"); # you may not use this file except in compliance with the License. diff --git a/cmd/kube-controller-manager/app/controllermanager.go b/cmd/kube-controller-manager/app/controllermanager.go index 52f7701d50c..513bbd70d59 100644 --- a/cmd/kube-controller-manager/app/controllermanager.go +++ b/cmd/kube-controller-manager/app/controllermanager.go @@ -1,6 +1,6 @@ /* Copyright 2014 The Kubernetes Authors. -Copyright 2020 Authors of Alkaid - file modified. +Copyright 2020 Authors of Arktos - file modified. Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. diff --git a/cmd/kube-controller-manager/app/core.go b/cmd/kube-controller-manager/app/core.go index 5deadd07037..bebf5c06062 100644 --- a/cmd/kube-controller-manager/app/core.go +++ b/cmd/kube-controller-manager/app/core.go @@ -1,6 +1,6 @@ /* Copyright 2016 The Kubernetes Authors. -Copyright 2020 Authors of Alkaid - file modified. +Copyright 2020 Authors of Arktos - file modified. Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. diff --git a/cmd/kubeadm/app/constants/constants.go b/cmd/kubeadm/app/constants/constants.go index 321f26bffeb..4627a02986b 100644 --- a/cmd/kubeadm/app/constants/constants.go +++ b/cmd/kubeadm/app/constants/constants.go @@ -1,6 +1,6 @@ /* Copyright 2019 The Kubernetes Authors. -Copyright 2020 Authors of Alkaid - file modified. +Copyright 2020 Authors of Arktos - file modified. Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. diff --git a/cmd/kubeadm/app/phases/copycerts/copycerts_test.go b/cmd/kubeadm/app/phases/copycerts/copycerts_test.go index de680142be8..90611403b48 100644 --- a/cmd/kubeadm/app/phases/copycerts/copycerts_test.go +++ b/cmd/kubeadm/app/phases/copycerts/copycerts_test.go @@ -1,6 +1,6 @@ /* Copyright 2019 The Kubernetes Authors. -Copyright 2020 Authors of Alkaid - file modified. +Copyright 2020 Authors of Arktos - file modified. Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. diff --git a/cmd/kubeadm/app/phases/upgrade/compute_test.go b/cmd/kubeadm/app/phases/upgrade/compute_test.go index 8917e6828db..ee6d5b462f9 100644 --- a/cmd/kubeadm/app/phases/upgrade/compute_test.go +++ b/cmd/kubeadm/app/phases/upgrade/compute_test.go @@ -1,6 +1,6 @@ /* Copyright 2017 The Kubernetes Authors. -Copyright 2020 Authors of Alkaid - file modified. +Copyright 2020 Authors of Arktos - file modified. Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. diff --git a/cmd/kubelet/app/server_bootstrap_test.go b/cmd/kubelet/app/server_bootstrap_test.go index 62bdb408631..309ef698839 100644 --- a/cmd/kubelet/app/server_bootstrap_test.go +++ b/cmd/kubelet/app/server_bootstrap_test.go @@ -1,6 +1,6 @@ /* Copyright 2016 The Kubernetes Authors. -Copyright 2020 Authors of Alkaid - file modified. +Copyright 2020 Authors of Arktos - file modified. Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. diff --git a/cmd/kubemark/hollow-node.go b/cmd/kubemark/hollow-node.go index 35926303ef4..ec9688c4003 100644 --- a/cmd/kubemark/hollow-node.go +++ b/cmd/kubemark/hollow-node.go @@ -1,6 +1,6 @@ /* Copyright 2015 The Kubernetes Authors. -Copyright 2020 Authors of Alkaid - file modified. +Copyright 2020 Authors of Arktos - file modified. Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. diff --git a/cmd/workload-controller-manager/app/config/config.go b/cmd/workload-controller-manager/app/config/config.go index 379ec383e7e..a89b9176114 100644 --- a/cmd/workload-controller-manager/app/config/config.go +++ b/cmd/workload-controller-manager/app/config/config.go @@ -1,5 +1,5 @@ /* -Copyright 2020 Authors of Alkaid. +Copyright 2020 Authors of Arktos. Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. diff --git a/cmd/workload-controller-manager/app/config/controllerconfig.go b/cmd/workload-controller-manager/app/config/controllerconfig.go index 2c4889e1222..689c00b6ee8 100644 --- a/cmd/workload-controller-manager/app/config/controllerconfig.go +++ b/cmd/workload-controller-manager/app/config/controllerconfig.go @@ -1,5 +1,5 @@ /* -Copyright 2020 Authors of Alkaid. +Copyright 2020 Authors of Arktos. Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. diff --git a/cmd/workload-controller-manager/app/controllermanager.go b/cmd/workload-controller-manager/app/controllermanager.go index 24ec977b9cb..0b3816d2d48 100644 --- a/cmd/workload-controller-manager/app/controllermanager.go +++ b/cmd/workload-controller-manager/app/controllermanager.go @@ -1,5 +1,5 @@ /* -Copyright 2020 Authors of Alkaid. +Copyright 2020 Authors of Arktos. Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. diff --git a/cmd/workload-controller-manager/app/helper.go b/cmd/workload-controller-manager/app/helper.go index 5640b8efe58..152b1e84309 100644 --- a/cmd/workload-controller-manager/app/helper.go +++ b/cmd/workload-controller-manager/app/helper.go @@ -1,5 +1,5 @@ /* -Copyright 2020 Authors of Alkaid. +Copyright 2020 Authors of Arktos. Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. diff --git a/cmd/workload-controller-manager/app/options/options.go b/cmd/workload-controller-manager/app/options/options.go index 407b901b1dd..d026b2293bb 100644 --- a/cmd/workload-controller-manager/app/options/options.go +++ b/cmd/workload-controller-manager/app/options/options.go @@ -1,5 +1,5 @@ /* -Copyright 2020 Authors of Alkaid. +Copyright 2020 Authors of Arktos. Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. diff --git a/cmd/workload-controller-manager/app/serve.go b/cmd/workload-controller-manager/app/serve.go index 5b22dbbc4b8..6868da05ad5 100644 --- a/cmd/workload-controller-manager/app/serve.go +++ b/cmd/workload-controller-manager/app/serve.go @@ -1,5 +1,5 @@ /* -Copyright 2020 Authors of Alkaid. +Copyright 2020 Authors of Arktos. Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. diff --git a/cmd/workload-controller-manager/main.go b/cmd/workload-controller-manager/main.go index 5753b17112d..67f2ee5961d 100644 --- a/cmd/workload-controller-manager/main.go +++ b/cmd/workload-controller-manager/main.go @@ -1,5 +1,5 @@ /* -Copyright 2020 Authors of Alkaid. +Copyright 2020 Authors of Arktos. Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. diff --git a/code-of-conduct.md b/code-of-conduct.md index 53b4581cdfe..aeb2a519922 100644 --- a/code-of-conduct.md +++ b/code-of-conduct.md @@ -1,5 +1,5 @@ -# Alkaid Community Code of Conduct +# Arktos Community Code of Conduct -Alkaid follows the [CNCF Code of Conduct](https://git.k8s.io/community/code-of-conduct.md). +Arktos follows the [CNCF Code of Conduct](https://git.k8s.io/community/code-of-conduct.md). -Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to [Alkaid Contacts](mailto:ying.xiong@futurewei.com). +Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to [Arktos Contacts](mailto:ying.xiong@futurewei.com). diff --git a/docs/design-proposals/apiserver/multi-tenancy.md b/docs/design-proposals/apiserver/multi-tenancy.md index bb937e62680..ce50c626eca 100644 --- a/docs/design-proposals/apiserver/multi-tenancy.md +++ b/docs/design-proposals/apiserver/multi-tenancy.md @@ -1,6 +1,6 @@ -# Multi-Tenancy in Alkaid +# Multi-Tenancy in Arktos Qian Chen, Xiaoning Ding @@ -9,7 +9,7 @@ Qian Chen, Xiaoning Ding Kubernetes provides a solution for automating deployment, scaling, and operations of application containers across clusters of hosts. However, it does not have support multi-tenancy. There is no explicit “tenant” concept in the system, and there is no resource isolation, usage isolation or performance isolation for different tenants. -Alkaid is evolved from Kubernetes but designed for public cloud. For a cluster management system supporting public cloud workloads, multi-tenancy is a fundamental requirement. This design document proposes works need to be done to support multi-tenancy for Alkaid. +Arktos is evolved from Kubernetes but designed for public cloud. For a cluster management system supporting public cloud workloads, multi-tenancy is a fundamental requirement. This design document proposes works need to be done to support multi-tenancy for Arktos. ## Hard Multi-Tenancy Model @@ -30,7 +30,7 @@ Our hard multi-tenancy model is one where: ### Tenant Object -A tenant is defined as a group of users/identities who have the exclusive access to its own resources in parallel to other tenants within an Alkaid system. A tenant can have one or multiple namespaces. Two namespaces can have the same name as long as they are under different tenants. +A tenant is defined as a group of users/identities who have the exclusive access to its own resources in parallel to other tenants within an Arktos system. A tenant can have one or multiple namespaces. Two namespaces can have the same name as long as they are under different tenants. A tenant is an API resource type. A sample yaml file is as follows. @@ -44,7 +44,7 @@ metadata: ### Resource Hierarchy -A resource in Alkaid belongs to one and only one of the following three scopes: +A resource in Arktos belongs to one and only one of the following three scopes: 1. Cluster scope 2. Tenant scope 3. Namespace scope @@ -83,7 +83,7 @@ spec: ``` ### API URLs -All Alkaid API URLs start with “/apis/{api-group-name}/{version}”, just like k8s. The API URLs for the resources of different scopes are as follows: +All Arktos API URLs start with “/apis/{api-group-name}/{version}”, just like k8s. The API URLs for the resources of different scopes are as follows: 1. Cluster-scoped resources can be addressed by “/apis/{api-group-name}/{version}/*”. 2. Tenant-scoped resources are addressed by paths like “/apis/{api-group-name}/{version}/tenants/{tenant}/*”. 3. Namespace-scoped resources are addressed by paths like “/apis/{api-group-name}/{version}/tenants/{tenant}/namespaces/{namespace}/*”. @@ -112,7 +112,7 @@ The key paths of the resources in backend ETCD will also vary according to their Two special tenants will be created automaticallyif they don’t exist. - 1. *System*. It is the tenant for the Alkaid system itself. + 1. *System*. It is the tenant for the Arktos system itself. 2. *Default*. If the tenant of a resource type is not defined, it will be assigned to the default tenant. @@ -127,7 +127,7 @@ When a tenant is created, two namespaces will be created under the tenant: ## Layered Access Control -Role-based access control (RBAC) model will remain in Alkaid, yet with more layers than in K8s. +Role-based access control (RBAC) model will remain in Arktos, yet with more layers than in K8s. In RBAC, a role contains rules that represent a set of permissions. Different scopes have different type of roles. It can be: 1. A Role within a namespace. A Role is used to grant access to resources within a single namespace. 2. A TenantRole within a tenant scope. A TenantRole can be used to grant the same permission as a Role. But it can also be used to grant access to @@ -136,7 +136,7 @@ In RBAC, a role contains rules that represent a set of permissions. Different sc b. Namespaced resources across multiple namespaces -3. A ClusterRole for the Alkaid system-wide scope. A ClusterRole can grant permissions to +3. A ClusterRole for the Arktos system-wide scope. A ClusterRole can grant permissions to a. Resources within a namespace or a tenant @@ -148,12 +148,12 @@ A role binding grants the permissions defined in a role to a user or a set of us ## Resource Quota Isolation -In k8s, the computation resources (such as cpu and memory) are provisioned via [ResourceQuota](https://kubernetes.io/docs/concepts/policy/resource-quotas/), which is an optional namespace-scope feature. Similar quota based resource provisioning mechanism will be implemented in Alkaid. Yet the resource quota control in the tenant level is mandatory, in order to guarantee the performance and usage isolation among different tenants. +In k8s, the computation resources (such as cpu and memory) are provisioned via [ResourceQuota](https://kubernetes.io/docs/concepts/policy/resource-quotas/), which is an optional namespace-scope feature. Similar quota based resource provisioning mechanism will be implemented in Arktos. Yet the resource quota control in the tenant level is mandatory, in order to guarantee the performance and usage isolation among different tenants. In more details: 1. ResourceQuota control is mandatory in the tenant level. Namely, every tenant must have the ResourceQuota set. If the quota are not specified by the user when creating the tenant, the system will set them to the default values. The resource quota control in the namespace levle is still optional. A namespace can choose to specify ResourceQuota or not. 2. A pod request will be accepted only if both the tenant and the namespace resource quota are not violated. In the case that the resource quota of the tenant is less than the sums of the quota of the namespaces, the requests are handled in a first-come-first-serve basis. -3. Quota control on more resource types will be supported. K8s 1.15 supports control on the resource of cpu and memory. As Alkaid will support both VMs and containers, resource control over resources like network bandwidth or the number of VMs should also be considered. Yet research on what resources need to be done is outside the scope of this doc and it will be covered by a different proposal. +3. Quota control on more resource types will be supported. K8s 1.15 supports control on the resource of cpu and memory. As Arktos will support both VMs and containers, resource control over resources like network bandwidth or the number of VMs should also be considered. Yet research on what resources need to be done is outside the scope of this doc and it will be covered by a different proposal. ## Usage and Performance Isolation @@ -272,7 +272,7 @@ Following are the list of resources belonging to each scope. Those highlighted w #### Namespace-Scoped resources: -The following namespace-scoped resources in k8s will continue to exist in Alkaid with similar functionalities, except that their objectMeta include the name of tenant now. +The following namespace-scoped resources in k8s will continue to exist in Arktos with similar functionalities, except that their objectMeta include the name of tenant now. 1. PersistentVolumeClaim 2. Pod 3. PodTemplate diff --git a/docs/design-proposals/network/NICAndVPCSupportInAlkaid.md b/docs/design-proposals/network/NICAndVPCSupportInArktos.md similarity index 92% rename from docs/design-proposals/network/NICAndVPCSupportInAlkaid.md rename to docs/design-proposals/network/NICAndVPCSupportInArktos.md index 65f5e4775d6..76e6c0f6041 100644 --- a/docs/design-proposals/network/NICAndVPCSupportInAlkaid.md +++ b/docs/design-proposals/network/NICAndVPCSupportInArktos.md @@ -1,29 +1,29 @@ -# NIC and VPC Support in Alkaid +# NIC and VPC Support in Arktos Xiaoning Ding, Hongwei Chen -This document describes the Network Interface Card (NIC) and Virtual Private Cloud (VPC) support in Alkaid, including motivation, pod spec changes and component changes. +This document describes the Network Interface Card (NIC) and Virtual Private Cloud (VPC) support in Arktos, including motivation, pod spec changes and component changes. ## Motivation -Alkaid is evolved from Kubernetes with the goal to support VM and container workloads in a unified way. And it's designed for public cloud only. This brings some new requirements for networking: +Arktos is evolved from Kubernetes with the goal to support VM and container workloads in a unified way. And it's designed for public cloud only. This brings some new requirements for networking: * In Kubernetes a pod doesn't need to specify its IP and NIC configuration. It relies on the underlying container networking provider to dynamically assign IPs, usually through an IPAM plugin, and then create NICs. This is suitable for containers. However, for VMs it's common to have static IP and NIC configurations, especially for some legacy VM deployments. -* Kubernetes can run with different networking solutions for different scenarios. But Alkaid is designed for public cloud only. Therefore, it's important to provide a native support for VPC networking of public cloud. +* Kubernetes can run with different networking solutions for different scenarios. But Arktos is designed for public cloud only. Therefore, it's important to provide a native support for VPC networking of public cloud. -The rest of the document explains how Alkaid supports NIC configurations on a pod, and how it interacts with VPC services to support NIC configurations. +The rest of the document explains how Arktos supports NIC configurations on a pod, and how it interacts with VPC services to support NIC configurations. ## Overview -As an underlying cluster management system in cloud data centers, Alkaid itself doesn't expose APIs to cloud users directly. Cloud users interact with public cloud services that are built on top of Alkaid, such as ECS or CCI services. These services then in turn call Alkaid APIs to manage workloads. +As an underlying cluster management system in cloud data centers, Arktos itself doesn't expose APIs to cloud users directly. Cloud users interact with public cloud services that are built on top of Arktos, such as ECS or CCI services. These services then in turn call Arktos APIs to manage workloads. -A workload in Alkaid is represented by a pod. An Alkaid pod can specify one or more **NICs**, and each Nic is mapped to a VPC **port** resource that is backed by a cloud VPC service. Users can associate a pod with an existing port, or let Alkaid to dynamically create and delete ports for a pod. +A workload in Arktos is represented by a pod. An Arktos pod can specify one or more **NICs**, and each Nic is mapped to a VPC **port** resource that is backed by a cloud VPC service. Users can associate a pod with an existing port, or let Arktos to dynamically create and delete ports for a pod. -A port is always attached to a certain subnet in a certain VPC, and may belong to one or more security groups. Lots of other VPC resources could impact the behavior of a VPC port as well, such as Network ACLs or Routing Rules. But the only VPC resource type that Alkaid manages is port. All other VPC resource types (such as subnets or security groups) are managed: +A port is always attached to a certain subnet in a certain VPC, and may belong to one or more security groups. Lots of other VPC resources could impact the behavior of a VPC port as well, such as Network ACLs or Routing Rules. But the only VPC resource type that Arktos manages is port. All other VPC resource types (such as subnets or security groups) are managed: * by cloud users directly calling VPC service APIs; * Or by a cloud service such as ECS calling VPC service APIs. @@ -32,12 +32,12 @@ The below diagram shows the relationship among these services: ![alt text](NICandVPC-Overview.png "Overview") -Alkaid supports different VPC implementations as long as they provide an API to manage the lifecycle of port resources. For now we support two different implementations: +Arktos supports different VPC implementations as long as they provide an API to manage the lifecycle of port resources. For now we support two different implementations: * OpenStack Neutron -* Alkaid Networking (Alcor) +* Arktos Networking (Alcor) -Different VPC implementation has different data plane components on computing hosts, and this requires different operations to attach a workload to the network. Alkaid leverages CNI plugin mechanism to support these different operations. +Different VPC implementation has different data plane components on computing hosts, and this requires different operations to attach a workload to the network. Arktos leverages CNI plugin mechanism to support these different operations. ## Pod Spec Changes @@ -210,7 +210,7 @@ Some additional checks need to be done in an admission controller: ### Controller Manager -A new Alkaid controller, network controller, will be introduced to create ports and delete ports. +A new Arktos controller, network controller, will be introduced to create ports and delete ports. Here is what the new network controller needs to do: @@ -241,7 +241,7 @@ The following changes are required: ### Neutron CNI Plugin -A new CNI plugin needs to be implemented to interact with the Neutron data plane components on Alkaid hosts. +A new CNI plugin needs to be implemented to interact with the Neutron data plane components on Arktos hosts. On a computing host Neutron agent has already setup required OVS bridges (br-int and br-tun) when it initializes. What the CNI plugin needs to do is initializing the per-port components and attaching/detaching it from these OVS bridges. @@ -264,11 +264,11 @@ The below diagram shows the ownership of above devices: Alcor has a much-simplified data plane components on each computing host. It basically creates a veth pair for each port, attaches its eBPF program to one end of the pair, and leaves the other end of the pair to pods. The other end of the veth pair will be listed in the host namespace as a virtual interface. -The current agreement between Alkaid and Alcor is: +The current agreement between Arktos and Alcor is: * The virtual interface will follow a naming rule. For example, "veth{11-char-prefix-of-portID}". * Alcor agent puts the virtual interface inside of VPC specific netns. The name of VPC specific netns should be "vpc-ns{full-vpc-id}" -* Once the virtual interface (one end of the veth pair created by Alcor agent) appears inside of the VPC netns, it means the preparation work on Alcor side has been done and the port is ready for Alkaid to use. +* Once the virtual interface (one end of the veth pair created by Alcor agent) appears inside of the VPC netns, it means the preparation work on Alcor side has been done and the port is ready for Arktos to use. Therefore, the Alcor CNI plugin only needs to query and wait until a virtual interface with the expected name appears in the host namespace. diff --git a/docs/design-proposals/network/vnic_hotplug.md b/docs/design-proposals/network/vnic_hotplug.md index 8dd27ef9b58..93f0e7cd983 100644 --- a/docs/design-proposals/network/vnic_hotplug.md +++ b/docs/design-proposals/network/vnic_hotplug.md @@ -5,7 +5,7 @@ vnic hotplug is the ability to allow admin of VM workload able to insert (plug i If the pod is intended to hotplug nic, its has to explicitly assign name to each nic in the initial pod spec. Otherwise, the pod won't be able to patched to request nic hotplugs. -In Alkaid, hotplug is only applicable to VM workloads. Hotplug should not apply to the primary nic (_note: to de decided_) +In Arktos, hotplug is only applicable to VM workloads. Hotplug should not apply to the primary nic (_note: to de decided_) Admin expresses the intention of hotplug by adding/removing pod.spec.vnics elements. diff --git a/docs/design-proposals/node/Support-multiple-runtimes.md b/docs/design-proposals/node/Support-multiple-runtimes.md index acae1a4e722..13e0464ff57 100644 --- a/docs/design-proposals/node/Support-multiple-runtimes.md +++ b/docs/design-proposals/node/Support-multiple-runtimes.md @@ -1,9 +1,9 @@ -# Multiple CRI runtime endpoint support in Alkaid node agent +# Multiple CRI runtime endpoint support in Arktos node agent ## Motivation -Alkaid is a unified compute platform to support both container and virtual machine workloads and to provide superior -resource allocation efficiency in the cluster, in addition to support large scale cluster. Therefore, the Alkaid node +Arktos is a unified compute platform to support both container and virtual machine workloads and to provide superior +resource allocation efficiency in the cluster, in addition to support large scale cluster. Therefore, the Arktos node agent needs to support both virtual machine and container runtime services, not only for containerizing applications that used to run on virtual machines, but also to support those workloads in a native way, which, in our opinions, should have the following characteristics: @@ -17,7 +17,7 @@ have the following characteristics: runtime services, despite of agent rebooting situations. For more information on the design for natively support of multiple runtimes and workloads, please refer to the -"Multiple runtime and workload types support in Alkaid node agent" document. +"Multiple runtime and workload types support in Arktos node agent" document. This spec describes the proposal for the phase 1,, to extend the current Kubernetes to support multiple runtime services by extending the current GenericRuntimeManager type and runtime manager interfaces. @@ -28,13 +28,13 @@ It allows cluster admins to provide RuntimeClasses to expose the multiple config the POD (workload) to specify the desired configuration to run the containers specified in the POD. It is also opened the ways for dynamic scheduling logic for a POD to node with the specific runtime configurations. However the runtimeClass is designed merely for containers and depends on CRI implementations and configurations. It does not fit the -requirements for Alkaid to support virtual machine runtime service natively. +requirements for Arktos to support virtual machine runtime service natively. Mirantis CRI Proxy, along with its CRI implementation(Virtlet) provides a way run multiple CRI implementations on the node. Essentially it provides a layer between the node agent and multiple CRI implementations. By intercepting the gRPC call from node agent, the CRI proxy redirect the CRI request to the desired CRI service and returns the response to the node agent. It provides a decent way to run multiple CRI services at the node without change the Kubelet internal -logic. However, the CRI proxy has a few limits that cannot fit the Alkaid's requirements: +logic. However, the CRI proxy has a few limits that cannot fit the Arktos's requirements: 1. It is designed merely for CRI implementation, with all the internal logic in Kubelet, it will be hard support virtual runtime services natively @@ -47,7 +47,7 @@ logic. However, the CRI proxy has a few limits that cannot fit the Alkaid's requ 1. Provide initial work to satisfy the characteristic of natively support multiple workload types, by allows multiple runtime endpoints configured by Cluster Admins and POD can choose desired runtime service to run 2. Legacy cluster(Kubelet commandline) should continue to work with the code change -3. Legacy applications(without the runtimeServiceName) should continue to work in Alkaid cluster +3. Legacy applications(without the runtimeServiceName) should continue to work in Arktos cluster ## Proposal @@ -189,12 +189,12 @@ The Kubelet changes can be categorized into a few areas: With the static runtime service registration, the node agent has to be restarted to load the new runtime service when a new runtime service is installed and available on the node. This is not ideal because it introduces downtime at the - node agent. (Future work) Alkaid node agent provides registration framework to allow dynamic registration of runtime + node agent. (Future work) Arktos node agent provides registration framework to allow dynamic registration of runtime service to avoid unnecessary downtime. -2. Advertise the supported runtime services to Alkaid users +2. Advertise the supported runtime services to Arktos users For the first release, this can be as simple as documentation to list the supported runtime services for container and - virtual machine workloads. For future releases, a configMap can be used so Alkaid users can query the supported runtime + virtual machine workloads. For future releases, a configMap can be used so Arktos users can query the supported runtime services in the cluster. 3. Support partial runtime services readiness diff --git a/docs/design-proposals/scalabilty-goals.md b/docs/design-proposals/scalabilty-goals.md index 3dcf1d7d527..6d839ac6a7a 100644 --- a/docs/design-proposals/scalabilty-goals.md +++ b/docs/design-proposals/scalabilty-goals.md @@ -2,13 +2,13 @@ _by Quinton Hoole_ -Based upon the original [Kubenetes SIG-Scalability Goals](https://github.com/kubernetes/community/blob/master/sig-scalability/goals.md), updated to 2019, and extended to cover Alkaid's extended goals. +Based upon the original [Kubenetes SIG-Scalability Goals](https://github.com/kubernetes/community/blob/master/sig-scalability/goals.md), updated to 2019, and extended to cover Arktos's extended goals. **October 2019** ## Introduction -What size clusters do we think that we should support with Alkaid in +What size clusters do we think that we should support with Arktos in the short to medium term? How performant do we think that the control system should be at scale? What resource overhead should the control system reasonably consume? This document attempts to answer these and diff --git a/docs/setup-guide/multi-node-dev-cluster.md b/docs/setup-guide/multi-node-dev-cluster.md index a7cbf7d731a..f31c925658f 100644 --- a/docs/setup-guide/multi-node-dev-cluster.md +++ b/docs/setup-guide/multi-node-dev-cluster.md @@ -1,13 +1,13 @@ # How to Setup a small Dev Cluster of multi-nodes -It may be desired to setup a dev cluster having 2 or 3 nodes in order to play with comprehansive features of Alkaid. The simple and easy-to-use alkaid-up.sh feels short in this case; this doc describes the minimum effort to run a cluster havinbg 2 nodes (1 master, plus a worker who joins later). +It may be desired to setup a dev cluster having 2 or 3 nodes in order to play with comprehansive features of Arktos. The simple and easy-to-use arktos-up.sh feels short in this case; this doc describes the minimum effort to run a cluster havinbg 2 nodes (1 master, plus a worker who joins later). This doc, as at the moment written, does not mandate which cni plugin to be used. It is up to user, though we recommend to use calico, or our own alktron. 1. start the master node the master node, run follwoing commands to start cluster, which has the master only. ```bash -./hack/alkaid-up.sh +./hack/arktos-up.sh ``` 2. copy needed files to worker node @@ -25,7 +25,7 @@ at worker node, run follwoing commands ```bash export KUBELET_IP= export KUBELET_KUBECONFIG= -./alkaid-worker-up.sh +./arktos-worker-up.sh ``` If kube-proxy is desired to run on worker, first make sure kube-proxy.yaml points to proper kube-proxy.kubeconfig, then run (note: for alktron as cni plugin, you don't need to run kube-proxy at all) diff --git a/docs/user-guide/features/nic_hotplug.md b/docs/user-guide/features/nic_hotplug.md index 781c119bf71..579ea6962cb 100644 --- a/docs/user-guide/features/nic_hotplug.md +++ b/docs/user-guide/features/nic_hotplug.md @@ -1,8 +1,8 @@ # Network Interface Hotplug -It is not rare that admin of virtual machine (vm for short) wants to dynamically add secondary network interfaces while the instance is still running; this hotplug ability is available from various hypersisors like qemu/kvm, vmware etc. Alkaid, our platform managing vm pods as the first class citizen as well as traditional container based ones, provides the similar feature of network interface hotplug. +It is not rare that admin of virtual machine (vm for short) wants to dynamically add secondary network interfaces while the instance is still running; this hotplug ability is available from various hypersisors like qemu/kvm, vmware etc. Arktos, our platform managing vm pods as the first class citizen as well as traditional container based ones, provides the similar feature of network interface hotplug. -This doc describes how secondary nic is plugged into a running vm instance in Alkaid, from the perspective of end user (vm admin). +This doc describes how secondary nic is plugged into a running vm instance in Arktos, from the perspective of end user (vm admin). ## Launching a vm pod VM pod is defined, in k8s way, by pod spec file. For vm pod that might have nic hotplug, there is a requirement of pod spec - nic __MUST be specified explicitly defined, and nic name MUST be present__. @@ -33,7 +33,7 @@ kubectl apply -f vm-nic-hotplug.yaml ``` ## Specify the secondary nic to plugin -NIC is one of the types of resources a pod has; in line of k8s spirit, pod spec keeps the desired state of resources, and Alkaid system (notably kubelet) identifies the actual state of resources, attempts to reconcile the difference between the actual and desired states. In case of nic, kubelet identifies the difference of the nic spec and nic status collected from the underlying runtime system, issues necessary commands to the runtime requesting attaching nic to specific vm instance. +NIC is one of the types of resources a pod has; in line of k8s spirit, pod spec keeps the desired state of resources, and Arktos system (notably kubelet) identifies the actual state of resources, attempts to reconcile the difference between the actual and desired states. In case of nic, kubelet identifies the difference of the nic spec and nic status collected from the underlying runtime system, issues necessary commands to the runtime requesting attaching nic to specific vm instance. Update of pod spec is specified as patch spec, denoted as patch-nic-hoptlug.yaml ```yaml diff --git a/hack/alkaid-apiserver-partition.sh b/hack/arktos-apiserver-partition.sh similarity index 94% rename from hack/alkaid-apiserver-partition.sh rename to hack/arktos-apiserver-partition.sh index c0fa9a79266..4ad9238767a 100644 --- a/hack/alkaid-apiserver-partition.sh +++ b/hack/arktos-apiserver-partition.sh @@ -1,7 +1,7 @@ #!/usr/bin/env bash -# Copyright 2020 Authors of Alkaid. +# Copyright 2020 Authors of Arktos. # # Licensed under the Apache License, Version 2.0 (the "License"); # you may not use this file except in compliance with the License. @@ -37,8 +37,8 @@ function apply_test_data { } function start_apiserver { - echo "Running alkaid-up.sh..." - source $(dirname "$0")/alkaid-up.sh + echo "Running arktos-up.sh..." + source $(dirname "$0")/arktos-up.sh } "$@" diff --git a/hack/alkaid-cni.rc b/hack/arktos-cni.rc similarity index 91% rename from hack/alkaid-cni.rc rename to hack/arktos-cni.rc index bca23c71a95..d56c7a81301 100644 --- a/hack/alkaid-cni.rc +++ b/hack/arktos-cni.rc @@ -1,6 +1,6 @@ #!/usr/bin/env bash -# Copyright 2020 Authors of Alkaid. +# Copyright 2020 Authors of Arktos. # # Licensed under the Apache License, Version 2.0 (the "License"); # you may not use this file except in compliance with the License. @@ -126,9 +126,9 @@ ensure_devstack() { } -install_alkaid_containerd() { - local CONTAINERD_DIR=$(dirname "$BASH_SOURCE[0]}")/../../alkaid-containerd - [ -d ${CONTAINERD_DIR} ] || die "alkaid-containerd repo not found. please clone futurewei-cloud/alkaid-containerd branch wip-pod-annotation-to-cni-args side by side with alkaid" +install_arktos_containerd() { + local CONTAINERD_DIR=$(dirname "$BASH_SOURCE[0]}")/../../arktos-containerd + [ -d ${CONTAINERD_DIR} ] || die "arktos-containerd repo not found. please clone futurewei-cloud/arktos-containerd branch wip-pod-annotation-to-cni-args side by side with arktos" if [ ! -x ${CONTAINERD_DIR}/bin/containerd ]; then echo "building alkdaid containerd..." pushd ${CONTAINERD_DIR} > /dev/null @@ -142,11 +142,11 @@ install_alkaid_containerd() { echo "stopping containerd shortly to replace the binary..." local containerd_path=$(which containerd) sudo systemctl stop containerd - local containerd_back_path=$(dirname ${containerd_path})/containerd_alkaid_backup + local containerd_back_path=$(dirname ${containerd_path})/containerd_arktos_backup sudo mv ${containerd_path} ${containerd_back_path} sudo cp ${CONTAINERD_DIR}/bin/containerd ${containerd_path} sudo systemctl start containerd - echo "warning: original containerd binary is saved to ${containerd_path})/containerd_alkaid_backup" + echo "warning: original containerd binary is saved to ${containerd_path})/containerd_arktos_backup" echo "...done" fi } @@ -158,17 +158,17 @@ cni_bin_dir=${CNI_BIN_DIR:-"/opt/cni/bin"} if [ "${CNIPLUGIN}" == "bridge" ]; then - echo "cni plugin is bridge; alkaid will use bridge to provision pod network" + echo "cni plugin is bridge; arktos will use bridge to provision pod network" install_cni_bridge elif [ "${CNIPLUGIN}" == "alktron" ]; then ensure_devstack - install_alkaid_containerd + install_arktos_containerd sudo systemctl stop libvirtd > /dev/null || true - echo "cni plug is alktron; alkaid will use alktron \(neutron plugin\) to provision pod network" + echo "cni plug is alktron; arktos will use alktron \(neutron plugin\) to provision pod network" install_cni_alktron install_loopback_cni else - echo "cni plugin is ${CNIPLUGIN}; alkaid onebox cannot use it out of box." 1>&2 + echo "cni plugin is ${CNIPLUGIN}; arktos onebox cannot use it out of box." 1>&2 echo "suggest to use bridge cni plugin." echo "if you really want to use this plugin, you need to config cni plugin by yourself." exit 1 diff --git a/hack/alkaid-onebox.rc b/hack/arktos-onebox.rc similarity index 81% rename from hack/alkaid-onebox.rc rename to hack/arktos-onebox.rc index be8fd7bda54..043a2d608e8 100644 --- a/hack/alkaid-onebox.rc +++ b/hack/arktos-onebox.rc @@ -1,6 +1,6 @@ #!/usr/bin/env bash -# Copyright 2020 Authors of Alkaid. +# Copyright 2020 Authors of Arktos. # # Licensed under the Apache License, Version 2.0 (the "License"); # you may not use this file except in compliance with the License. @@ -15,11 +15,11 @@ # limitations under the License. -# Configure networking option of alkaid dev onebox -# This rc script is supposed to source before running alkaid-up.sh +# Configure networking option of arktos dev onebox +# This rc script is supposed to source before running arktos-up.sh # which cni plugin to use -# alkaid-up.sh supports 2 plugins out of box: bridge(default), alktron +# arktos-up.sh supports 2 plugins out of box: bridge(default), alktron #export CNIPLUGIN=bridge # alktron plugin authentication info for Devstack Keystone/Neutron diff --git a/hack/alkaid-up.sh b/hack/arktos-up.sh similarity index 99% rename from hack/alkaid-up.sh rename to hack/arktos-up.sh index 0541b49f831..2d4f934d367 100755 --- a/hack/alkaid-up.sh +++ b/hack/arktos-up.sh @@ -1,6 +1,6 @@ #!/usr/bin/env bash -# Copyright 2020 Authors of Alkaid. +# Copyright 2020 Authors of Arktos. # # Licensed under the Apache License, Version 2.0 (the "License"); # you may not use this file except in compliance with the License. @@ -194,7 +194,7 @@ if [ "${APPARMOR_ENABLED}" == "true" ]; then fi # install runtime apparmor profiles and reload apparmor - echo "Intalling alkaid runtime apparmor profiles" + echo "Intalling arktos runtime apparmor profiles" APPARMOR_PROFILE_DIR=${KUBE_ROOT}/hack/runtime/apparmor cp ${APPARMOR_PROFILE_DIR}/libvirt-qemu /etc/apparmor.d/abstractions/ sudo install -m 0644 ${APPARMOR_PROFILE_DIR}/libvirtd ${APPARMOR_PROFILE_DIR}/virtlet ${APPARMOR_PROFILE_DIR}/vms -t /etc/apparmor.d/ @@ -217,7 +217,7 @@ else fi # install cni plugin based on env var CNIPLUGIN (bridge, alktron) -source ${KUBE_ROOT}/hack/alkaid-cni.rc +source ${KUBE_ROOT}/hack/arktos-cni.rc source "${KUBE_ROOT}/hack/lib/init.sh" kube::util::ensure-gnu-sed @@ -1212,7 +1212,7 @@ if [[ "${DEFAULT_STORAGE_CLASS}" = "true" ]]; then fi echo "*******************************************" -echo "Setup Alkaid components ..." +echo "Setup Arktos components ..." echo "" while ! cluster/kubectl.sh get nodes --no-headers | grep -i -w Ready; do sleep 3; echo "Waiting for node ready at api server"; done @@ -1226,7 +1226,7 @@ cluster/kubectl.sh create -f hack/runtime/vmruntime.yaml cluster/kubectl.sh get ds --namespace kube-system echo "" -echo "Alkaid Setup done." +echo "Arktos Setup done." echo "*******************************************" echo "Setup Kata Containers components ..." "${KUBE_ROOT}"/hack/install-kata.sh diff --git a/hack/alkaid-worker-up.sh b/hack/arktos-worker-up.sh similarity index 97% rename from hack/alkaid-worker-up.sh rename to hack/arktos-worker-up.sh index d2e5a59631b..b37583bcbc6 100644 --- a/hack/alkaid-worker-up.sh +++ b/hack/arktos-worker-up.sh @@ -1,6 +1,6 @@ #!/usr/bin/env bash -# Copyright 2020 Authors of Alkaid. +# Copyright 2020 Authors of Arktos. # # Licensed under the Apache License, Version 2.0 (the "License"); # you may not use this file except in compliance with the License. diff --git a/hack/alkaid_copyright.sh b/hack/arktos_copyright.sh similarity index 75% rename from hack/alkaid_copyright.sh rename to hack/arktos_copyright.sh index 1b8aa97844e..f163623bd6e 100755 --- a/hack/alkaid_copyright.sh +++ b/hack/arktos_copyright.sh @@ -1,6 +1,6 @@ #!/bin/bash -e -# Copyright 2020 Authors of Alkaid. +# Copyright 2020 Authors of Arktos. # # Licensed under the Apache License, Version 2.0 (the "License"); # you may not use this file except in compliance with the License. @@ -14,25 +14,25 @@ # See the License for the specific language governing permissions and # limitations under the License. -ALKAID_COPYRIGHT_LINE_NEW_GO="Copyright 2020 Authors of Alkaid." -ALKAID_COPYRIGHT_LINE_NEW_OTHER="# Copyright 2020 Authors of Alkaid." -ALKAID_COPYRIGHT_LINE_MODIFIED_GO="Copyright 2020 Authors of Alkaid - file modified." -ALKAID_COPYRIGHT_LINE_MODIFIED_OTHER="# Copyright 2020 Authors of Alkaid - file modified." +ALKAID_COPYRIGHT_LINE_NEW_GO="Copyright 2020 Authors of Arktos." +ALKAID_COPYRIGHT_LINE_NEW_OTHER="# Copyright 2020 Authors of Arktos." +ALKAID_COPYRIGHT_LINE_MODIFIED_GO="Copyright 2020 Authors of Arktos - file modified." +ALKAID_COPYRIGHT_LINE_MODIFIED_OTHER="# Copyright 2020 Authors of Arktos - file modified." K8S_COPYRIGHT_MATCH="The Kubernetes Authors" -ALKAID_COPYRIGHT_MATCH="Authors of Alkaid" +ALKAID_COPYRIGHT_MATCH="Authors of Arktos" -ALKAID_REPO="https://github.com/futurewei-cloud/alkaid" -TMPDIR="/tmp/AlkaidCopyright" +ALKAID_REPO="https://github.com/futurewei-cloud/arktos" +TMPDIR="/tmp/ArktosCopyright" HEADDIRNAME="HEAD" REPODIRNAME=$TMPDIR/$HEADDIRNAME -LOGFILENAME="AlkaidCopyrightTool.log" +LOGFILENAME="ArktosCopyrightTool.log" LOGDIR=$TMPDIR LOGFILE=$LOGDIR/$LOGFILENAME EXIT_ERROR=0 display_usage() { - echo "Usage: $0 " - echo " If optional Alkaid repo path is provided, repo setup step will be skipped" + echo "Usage: $0 " + echo " If optional Arktos repo path is provided, repo setup step will be skipped" } if [ ! -z $1 ] @@ -74,9 +74,9 @@ get_added_files_list() { local HEAD_COMMIT=`git rev-list HEAD | head -n 1` git diff --name-only --diff-filter=A $DAY0_COMMIT $HEAD_COMMIT | \ egrep -v "\.git|\.md|\.bazelrc|\.json|\.pb|\.yaml|BUILD|boilerplate|vendor\/" | \ - egrep -v "\.mod|\.sum|\.png|\.PNG|OWNERS|alkaid_copyright" > $LOGDIR/added_files_git - grep -F -x -v -f $REPODIRNAME/hack/alkaid_copyright_copied_k8s_files $LOGDIR/added_files_git > $LOGDIR/added_files_less_copied - grep -F -x -v -f $REPODIRNAME/hack/alkaid_copyright_copied_modified_k8s_files $LOGDIR/added_files_less_copied > $LOGDIR/added_files + egrep -v "\.mod|\.sum|\.png|\.PNG|OWNERS|arktos_copyright" > $LOGDIR/added_files_git + grep -F -x -v -f $REPODIRNAME/hack/arktos_copyright_copied_k8s_files $LOGDIR/added_files_git > $LOGDIR/added_files_less_copied + grep -F -x -v -f $REPODIRNAME/hack/arktos_copyright_copied_modified_k8s_files $LOGDIR/added_files_less_copied > $LOGDIR/added_files popd } @@ -87,11 +87,11 @@ get_modified_files_list() { git diff --name-only --diff-filter=M $DAY0_COMMIT $HEAD_COMMIT | \ egrep -v "\.git|\.md|\.bazelrc|\.json|\.pb|\.yaml|BUILD|boilerplate|vendor\/" | \ egrep -v "\.mod|\.sum|\.png|\.PNG|OWNERS" > $LOGDIR/changed_files - cat $REPODIRNAME/hack/alkaid_copyright_copied_modified_k8s_files >> $LOGDIR/changed_files + cat $REPODIRNAME/hack/arktos_copyright_copied_modified_k8s_files >> $LOGDIR/changed_files popd } -replace_k8s_copyright_with_alkaid_copyright() { +replace_k8s_copyright_with_arktos_copyright() { local REPOFILE=$1 if [[ $REPOFILE = *.go ]] then @@ -101,7 +101,7 @@ replace_k8s_copyright_with_alkaid_copyright() { fi } -check_and_add_alkaid_copyright() { +check_and_add_arktos_copyright() { local REPOFILE=$1 set +e cat $REPOFILE | grep "$K8S_COPYRIGHT_MATCH" > /dev/null 2>&1 @@ -110,24 +110,24 @@ check_and_add_alkaid_copyright() { cat $REPOFILE | grep "$ALKAID_COPYRIGHT_MATCH" > /dev/null 2>&1 if [ $? -eq 0 ] then - echo "ERROR: Added file $REPOFILE has both K8s and Alkaid copyright." >> $LOGFILE + echo "ERROR: Added file $REPOFILE has both K8s and Arktos copyright." >> $LOGFILE else - echo "WARN: Added file $REPOFILE has K8s copyright and not Alkaid copyright. Replacing." >> $LOGFILE - replace_k8s_copyright_with_alkaid_copyright $REPOFILE + echo "WARN: Added file $REPOFILE has K8s copyright and not Arktos copyright. Replacing." >> $LOGFILE + replace_k8s_copyright_with_arktos_copyright $REPOFILE fi else cat $REPOFILE | grep "$ALKAID_COPYRIGHT_MATCH" > /dev/null 2>&1 if [ $? -eq 0 ] then - echo "Added file $REPOFILE has only Alkaid copyright. Skipping." >> $LOGFILE + echo "Added file $REPOFILE has only Arktos copyright. Skipping." >> $LOGFILE else - echo "ERROR: Added file $REPOFILE does not have either K8s or Alkaid copyright." >> $LOGFILE + echo "ERROR: Added file $REPOFILE does not have either K8s or Arktos copyright." >> $LOGFILE fi fi set -e } -update_alkaid_copyright() { +update_arktos_copyright() { local REPOFILE=$1 if [[ $REPOFILE = *.go ]] then @@ -137,7 +137,7 @@ update_alkaid_copyright() { fi } -check_and_update_alkaid_copyright() { +check_and_update_arktos_copyright() { local REPOFILE=$1 set +e cat $REPOFILE | grep "$K8S_COPYRIGHT_MATCH" > /dev/null 2>&1 @@ -146,10 +146,10 @@ check_and_update_alkaid_copyright() { cat $REPOFILE | grep "$ALKAID_COPYRIGHT_MATCH" > /dev/null 2>&1 if [ $? -eq 0 ] then - echo "Modified file $REPOFILE has both K8s and Alkaid copyright. Skipping." >> $LOGFILE + echo "Modified file $REPOFILE has both K8s and Arktos copyright. Skipping." >> $LOGFILE else - echo "Modified file $REPOFILE has K8s copyright but not Alkaid copyright. Patching." >> $LOGFILE - update_alkaid_copyright $REPOFILE + echo "Modified file $REPOFILE has K8s copyright but not Arktos copyright. Patching." >> $LOGFILE + update_arktos_copyright $REPOFILE fi else echo "Modified file $REPOFILE does not have K8s copyright. Skipping." >> $LOGFILE @@ -166,10 +166,10 @@ verify_copied_file_copyright() { cat $REPOFILE | grep "$ALKAID_COPYRIGHT_MATCH" > /dev/null 2>&1 if [ $? -eq 0 ] then - echo "WARN: Copied file $REPOFILE has both K8s and Alkaid copyright. Patching." >> $LOGFILE + echo "WARN: Copied file $REPOFILE has both K8s and Arktos copyright. Patching." >> $LOGFILE sed -i "/$ALKAID_COPYRIGHT_MATCH/d" $REPOFILE else - echo "Copied file $REPOFILE has K8s copyright but not Alkaid copyright. Skipping." >> $LOGFILE + echo "Copied file $REPOFILE has K8s copyright but not Arktos copyright. Skipping." >> $LOGFILE fi else echo "ERROR: Copied file $REPOFILE does not have K8s copyright. Please fix manually." >> $LOGFILE @@ -179,7 +179,7 @@ verify_copied_file_copyright() { set -e } -add_alkaid_copyright() { +add_arktos_copyright() { echo "Inspecting copyright files, writing logs to $LOGFILE" rm -f $LOGFILE local ADDED_FILELIST=$1 @@ -189,14 +189,14 @@ add_alkaid_copyright() { do if [ ! -z $line ] then - check_and_update_alkaid_copyright $REPODIRNAME/$line + check_and_update_arktos_copyright $REPODIRNAME/$line fi done < $CHANGED_FILELIST while IFS= read -r line do if [ ! -z $line ] then - check_and_add_alkaid_copyright $REPODIRNAME/$line + check_and_add_arktos_copyright $REPODIRNAME/$line fi done < $ADDED_FILELIST while IFS= read -r line @@ -217,6 +217,6 @@ fi get_added_files_list get_modified_files_list -add_alkaid_copyright $LOGDIR/added_files $LOGDIR/changed_files $REPODIRNAME/hack/alkaid_copyright_copied_k8s_files +add_arktos_copyright $LOGDIR/added_files $LOGDIR/changed_files $REPODIRNAME/hack/arktos_copyright_copied_k8s_files exit $EXIT_ERROR diff --git a/hack/alkaid_copyright_copied_k8s_files b/hack/arktos_copyright_copied_k8s_files similarity index 100% rename from hack/alkaid_copyright_copied_k8s_files rename to hack/arktos_copyright_copied_k8s_files diff --git a/hack/alkaid_copyright_copied_modified_k8s_files b/hack/arktos_copyright_copied_modified_k8s_files similarity index 100% rename from hack/alkaid_copyright_copied_modified_k8s_files rename to hack/arktos_copyright_copied_modified_k8s_files diff --git a/hack/boilerplate/boilerplate.py b/hack/boilerplate/boilerplate.py index 132ab6bdb13..96144b53492 100755 --- a/hack/boilerplate/boilerplate.py +++ b/hack/boilerplate/boilerplate.py @@ -1,7 +1,7 @@ #!/usr/bin/env python # Copyright 2015 The Kubernetes Authors. -# Copyright 2020 Authors of Alkaid - file modified. +# Copyright 2020 Authors of Arktos - file modified. # # Licensed under the Apache License, Version 2.0 (the "License"); # you may not use this file except in compliance with the License. @@ -106,10 +106,10 @@ def file_passes(filename, refs, regexs): data = data.splitlines() - # Skip Alkaid added file, remove Alkaid copyright for modified files + # Skip Arktos added file, remove Arktos copyright for modified files idx = 0 while idx < len(data): - if "Authors of Alkaid" in data[idx]: + if "Authors of Arktos" in data[idx]: if idx == 0 or "The Kubernetes Authors" not in data[idx-1]: return True del data[idx] diff --git a/hack/grab-profiles.sh b/hack/grab-profiles.sh index 3fc17d57933..920d655e458 100755 --- a/hack/grab-profiles.sh +++ b/hack/grab-profiles.sh @@ -1,7 +1,7 @@ #!/usr/bin/env bash # Copyright 2015 The Kubernetes Authors. -# Copyright 2020 Authors of Alkaid - file modified. +# Copyright 2020 Authors of Arktos - file modified. # # Licensed under the Apache License, Version 2.0 (the "License"); # you may not use this file except in compliance with the License. diff --git a/hack/install-kata.sh b/hack/install-kata.sh index 0172b0dadbd..b323bc5cd3a 100755 --- a/hack/install-kata.sh +++ b/hack/install-kata.sh @@ -1,6 +1,6 @@ #!/bin/bash -# Copyright 2020 Authors of Alkaid. +# Copyright 2020 Authors of Arktos. # # Licensed under the Apache License, Version 2.0 (the "License"); # you may not use this file except in compliance with the License. diff --git a/hack/lib/golang.sh b/hack/lib/golang.sh index d5c2aa12381..cc06deb740a 100755 --- a/hack/lib/golang.sh +++ b/hack/lib/golang.sh @@ -1,7 +1,7 @@ #!/usr/bin/env bash # Copyright 2014 The Kubernetes Authors. -# Copyright 2020 Authors of Alkaid - file modified. +# Copyright 2020 Authors of Arktos - file modified. # # Licensed under the Apache License, Version 2.0 (the "License"); # you may not use this file except in compliance with the License. diff --git a/hack/runtime/apparmor/README.md b/hack/runtime/apparmor/README.md index a6daa09d37f..8a623aecca8 100644 --- a/hack/runtime/apparmor/README.md +++ b/hack/runtime/apparmor/README.md @@ -1,5 +1,5 @@ # the apparmor filed taken from virtlet github -# with modification in the virtlet profile for the change to alter the /etc/resolv.conf file for alkaid +# with modification in the virtlet profile for the change to alter the /etc/resolv.conf file for arktos # AppArmor profiles diff --git a/hack/runtime/vmruntime.yaml b/hack/runtime/vmruntime.yaml index b3c8040f4f6..afa0d1591e7 100644 --- a/hack/runtime/vmruntime.yaml +++ b/hack/runtime/vmruntime.yaml @@ -38,13 +38,13 @@ spec: values: - virtlet imagePullSecrets: - - name: repo-alkaidstaging + - name: repo-arktosstaging initContainers: # The init container copies virtlet's flexvolume driver # to the default kubelet plugin dir and ensures that # the directories needed by libvirt & virtlet exist on the host - name: prepare-node - image: alkaidstaging/vmruntime:0.5.2 + image: arktosstaging/vmruntime:0.5.2 imagePullPolicy: IfNotPresent command: - /prepare-node.sh @@ -138,7 +138,7 @@ spec: containers: - name: libvirt - image: alkaidstaging/vmruntime:0.5.2 + image: arktosstaging/vmruntime:0.5.2 # In case we inject local virtlet image we want to use it not officially available one imagePullPolicy: IfNotPresent command: @@ -181,7 +181,7 @@ spec: - -c - socat - UNIX:/var/run/libvirt/libvirt-sock-ro