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.

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

proposal: add ingress feature support to nodepool #373

Merged
merged 1 commit into from
Jul 13, 2021

Conversation

zzguang
Copy link
Member

@zzguang zzguang commented Jul 1, 2021

Signed-off-by: zhenggu1 zhengguang.zhang@intel.com

What type of PR is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespace from that line:
/kind bug
/kind documentation
/kind enhancement
/kind good-first-issue
/kind feature
/kind question
/kind design
/sig ai
/sig iot
/sig network
/sig storage
/sig storage

What this PR does / why we need it:

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?


other Note

Signed-off-by: zhenggu1 <zhengguang.zhang@intel.com>
@openyurt-bot
Copy link
Collaborator

@zzguang: GitHub didn't allow me to assign the following users: your_reviewer.

Note that only openyurtio members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

Signed-off-by: zhenggu1 zhengguang.zhang@intel.com

What type of PR is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespace from that line:
/kind bug
/kind documentation
/kind enhancement
/kind good-first-issue
/kind feature
/kind question
/kind design
/sig ai
/sig iot
/sig network
/sig storage
/sig storage

What this PR does / why we need it:

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?


other Note

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openyurt-bot openyurt-bot added the size/L size/L: 100-499 label Jul 1, 2021
@openyurt-bot openyurt-bot requested review from Peeknut and yixingjia July 1, 2021 07:08
@zzguang
Copy link
Member Author

zzguang commented Jul 1, 2021

/assign @rambohe-ch

@wenjun93
Copy link
Member

wenjun93 commented Jul 2, 2021

/lgtm

@rambohe-ch
Copy link
Member

@zzguang Very appreciate for your proposal. and I am also agree with solution4.

@wenjun93
Copy link
Member

wenjun93 commented Jul 2, 2021

@zzguang the high level nodepool workload api cannot support customized configmaps in current stage, we might consider using one shared nginx config instead of customized configs among nodepools.

```yaml
nodepool.openyurt.io/ingress-ips: "xxx"
```
- When it detects the NodePool annotation below is changed, it will update the corresponding configmap of the NodePool,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If the workloads in NodePool use different configmaps, NodePool daemonset resource need to support different configmap setting. so how about create different configmaps directly by user instead of setting NodePool ingress-config?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

About the details design for implementation, it's just a draft version by now. We will investigate more to make it clear.
Thanks for your suggestion, we will take it into account.

@zzguang
Copy link
Member Author

zzguang commented Jul 2, 2021

@zzguang the high level nodepool workload api cannot support customized configmaps in current stage, we might consider using one shared nginx config instead of customized configs among nodepools.

Okay, we can consider to use a global nginx config for all the nodepools, then we need to figure out 2 problems:

  1. Who is responsible to create the configmap
  2. Whether it is popular that different nodepool needs some personalized configuration
    Thanks!

@rambohe-ch
Copy link
Member

/approve

and @zzguang will share this proposal in OpenYurt community meeting on July 21.

@openyurt-bot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rambohe-ch, zzguang

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:

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

@openyurt-bot openyurt-bot added the approved approved label Jul 13, 2021
@openyurt-bot openyurt-bot merged commit bff9847 into openyurtio:master Jul 13, 2021
zzguang referenced this pull request in zzguang/openyurt Jan 23, 2022
Signed-off-by: zhenggu1 <zhengguang.zhang@intel.com>
@zzguang zzguang mentioned this pull request Jan 23, 2022
6 tasks
MrGirl pushed a commit to MrGirl/openyurt that referenced this pull request Mar 29, 2022
Signed-off-by: zhenggu1 <zhengguang.zhang@intel.com>
@zzguang zzguang mentioned this pull request Jul 15, 2022
6 tasks
@zzguang zzguang mentioned this pull request Jul 25, 2022
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved approved lgtm lgtm size/L size/L: 100-499
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants