Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Support to directly deploy multi-cluster-ingress-nginx in production env #9

Open
lonelyCZ opened this issue Jun 13, 2022 · 9 comments
Open

Support to directly deploy multi-cluster-ingress-nginx in production env #9

lonelyCZ opened this issue Jun 13, 2022 · 9 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@lonelyCZ
Copy link
Member

I want to directly deploy multi-cluster-ingress-nginx in production env, not to use make dev-env.

Whether can it support official multi-cluster-ingress-nginx image, or using directly ingress-nginx image?
@lonelyCZ lonelyCZ added the kind/feature Categorizes issue or PR as related to a new feature. label Jun 13, 2022
@XiShanYongYe-Chang
Copy link
Member

We can make an image with the command: make build image.

For now, we have not released the multi-cluster-ingress-nginx image.

@RainbowMango
Copy link
Member

I want to directly deploy multi-cluster-ingress-nginx in production env

really?

@lonelyCZ
Copy link
Member Author

I want to directly deploy multi-cluster-ingress-nginx in production env

really?

It is a assumption. However, recently, we are going to deploy a whole multi-cluster manager system as a demonstration demo that need to include all multi-cluster function.

@RainbowMango
Copy link
Member

Good.
Then, we can publish the image.

@lonelyCZ
Copy link
Member Author

lonelyCZ commented Jun 14, 2022 •
edited
Loading

We can make an image with the command: make build image.

It seems always to request k8s.gcr.io when executing make, which could trouble domestic users.

[root@master137 multi-cluster-ingress-nginx]# make dev-env
[dev-env] building image
Unable to find image 'k8s.gcr.io/ingress-nginx/e2e-test-runner:v20220110-gfd820db46@sha256:273f7d9b1b2297cd96b4d51600e45d932186a1cc79d00d179dfb43654112fe8f' locally
docker: Error response from daemon: Get "https://k8s.gcr.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers).
See 'docker run --help'.
make[1]: *** [build] Error 125
make: *** [dev-env] Error 2
[root@master137 multi-cluster-ingress-nginx]# make build image
Unable to find image 'k8s.gcr.io/ingress-nginx/e2e-test-runner:v20220110-gfd820db46@sha256:273f7d9b1b2297cd96b4d51600e45d932186a1cc79d00d179dfb43654112fe8f' locally
docker: Error response from daemon: Get "https://k8s.gcr.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers).
See 'docker run --help'.
make: *** [build] Error 125

Perhaps, we need to provide a script or helm chart to deploy it in the future.

@XiShanYongYe-Chang
Copy link
Member

Perhaps, we need to provide a script or helm chart to deploy it in the future.

Nice! It would be convenient.

@lonelyCZ
Copy link
Member Author

It seems to timeout when make build image, how to resolve it? @XiShanYongYe-Chang

[root@master137 multi-cluster-ingress-nginx]# make build image
Building targets for amd64, generated targets in rootfs/bin/amd64 directory.
go: downloading github.com/prometheus/client_golang v1.11.0
go: downloading github.com/karmada-io/karmada v1.0.1-0.20220223011104-0c043f636ff3
go: downloading github.com/spf13/pflag v1.0.5
go: downloading k8s.io/apimachinery v0.23.4
go: downloading k8s.io/api v0.23.4
go: downloading k8s.io/apiserver v0.23.4
go: downloading k8s.io/client-go v0.23.4
go: downloading k8s.io/klog/v2 v2.30.0
go: downloading gopkg.in/go-playground/pool.v3 v3.1.1
go: downloading github.com/mitchellh/go-ps v1.0.0
go: downloading github.com/armon/go-proxyproto v0.0.0-20210323213023-7e956b284f0a
go: downloading github.com/eapache/channels v1.1.0
go: downloading github.com/mitchellh/hashstructure v1.1.0
go: downloading github.com/ncabatoff/process-exporter v0.7.10
go: downloading pault.ag/go/sniff v0.0.0-20200207005214-cf7e4d167732
go: downloading github.com/zakjan/cert-chain-resolver v0.0.0-20211122211144-c6b0b792af9a
go: downloading github.com/opencontainers/runc v1.0.3
go: downloading github.com/json-iterator/go v1.1.12
go: downloading github.com/prometheus/client_model v0.2.0
go: downloading github.com/prometheus/common v0.31.1
go: downloading github.com/imdario/mergo v0.3.12
go: downloading github.com/mitchellh/mapstructure v1.4.3
go: downloading github.com/fsnotify/fsnotify v1.5.1
internal/ingress/controller/nginx.go:38:2: github.com/armon/[email protected]: Get "https://proxy.golang.org/github.com/armon/go-proxyproto/@v/v0.0.0-20210323213023-7e956b284f0a.zip": dial tcp 142.251.43.17:443: i/o timeout
internal/ingress/controller/nginx.go:39:2: github.com/eapache/[email protected]: Get "https://proxy.golang.org/github.com/eapache/channels/@v/v1.1.0.zip": dial tcp 172.217.163.49:443: i/o timeout
internal/watch/file_watcher.go:26:2: github.com/fsnotify/[email protected]: Get "https://proxy.golang.org/github.com/fsnotify/fsnotify/@v/v1.5.1.zip": dial tcp 142.251.43.17:443: i/o timeout
internal/ingress/annotations/annotations.go:20:2: github.com/imdario/[email protected]: Get "https://proxy.golang.org/github.com/imdario/mergo/@v/v0.3.12.zip": dial tcp 142.251.43.17:443: i/o timeout
internal/ingress/metric/collectors/socket.go:26:2: github.com/json-iterator/[email protected]: Get "https://proxy.golang.org/github.com/json-iterator/go/@v/v1.1.12.zip": dial tcp 172.217.163.49:443: i/o timeout
internal/ingress/annotations/parser/main.go:25:2: github.com/karmada-io/[email protected]: Get "https://proxy.golang.org/github.com/karmada-io/karmada/@v/v1.0.1-0.20220223011104-0c043f636ff3.zip": dial tcp 142.251.43.17:443: i/o timeout
cmd/nginx/main.go:32:2: github.com/karmada-io/[email protected]: Get "https://proxy.golang.org/github.com/karmada-io/karmada/@v/v1.0.1-0.20220223011104-0c043f636ff3.zip": dial tcp 142.251.43.17:443: i/o timeout
internal/ingress/controller/store/store.go:33:2: github.com/karmada-io/[email protected]: Get "https://proxy.golang.org/github.com/karmada-io/karmada/@v/v1.0.1-0.20220223011104-0c043f636ff3.zip": dial tcp 142.251.43.17:443: i/o timeout
internal/ingress/controller/nginx.go:40:2: github.com/karmada-io/[email protected]: Get "https://proxy.golang.org/github.com/karmada-io/karmada/@v/v1.0.1-0.20220223011104-0c043f636ff3.zip": dial tcp 142.251.43.17:443: i/o timeout
internal/ingress/controller/controller_mci.go:10:2: github.com/karmada-io/[email protected]: Get "https://proxy.golang.org/github.com/karmada-io/karmada/@v/v1.0.1-0.20220223011104-0c043f636ff3.zip": dial tcp 142.251.43.17:443: i/o timeout
internal/nginx/main.go:30:2: github.com/mitchellh/[email protected]: Get "https://proxy.golang.org/github.com/mitchellh/go-ps/@v/v1.0.0.zip": dial tcp 172.217.163.49:443: i/o timeout
......

@XiShanYongYe-Chang
Copy link
Member

For reference, we can view the PR on Karmada repository: karmada-io/karmada#1925

@lonelyCZ
Copy link
Member Author

For reference, we can view the PR on Karmada repository: karmada-io/karmada#1925

Wow, looks great!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@RainbowMango @lonelyCZ @XiShanYongYe-Chang