Skip to content
This repository has been archived by the owner on Jun 5, 2024. It is now read-only.

Multi-nodes setup failed on notary-server #3

Open
darren-teoh opened this issue Nov 1, 2021 · 3 comments
Open

Multi-nodes setup failed on notary-server #3

darren-teoh opened this issue Nov 1, 2021 · 3 comments

Comments

@darren-teoh
Copy link

I manage to deploy single node SEO now. But face this issue when trying to deploy multi-node.

  • harbor-app: notary-server pod failed due to "node-role.kubernetes.io/master: pod didn't tolerate.
  • When i check the log file, I found that “node-role.kubernetes.io/master(deprecated), [NoSchedule]"
  • note that this is harbor notary version v2.3.2, i have setup docker.config with proxy setting of Intel.

Kindly check the image & logs file attached.
harbor_app_notary-server_failed_no_pod
kubectl_get_all
dek_test_dek_2021-10-29_14-33-11_network_edge.yml.log

@architag21
Copy link

DEK is supported only for single node deployment.

@yshashix
Copy link

yshashix commented Jul 1, 2022

Do you have any plan to bring it as clusters like k8s master and worker nodes?

@joez
Copy link

joez commented Apr 1, 2023

@yshashix SEO does support mulit-node cluster, but not documented officially, you can check this: Deploy Intel® Smart Edge Open Developer Experience Kit in a Multi-node Cluster without Edge Software Provisioner (ESP)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants