Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 24 additions & 0 deletions .github/workflows/go.yml
Original file line number Diff line number Diff line change
Expand Up @@ -31,3 +31,27 @@ jobs:
env:
GITHUB_TOKEN: ${{ secrets.GH_TOKEN }}
VERSION: latest
- name: set up buildx
id: buildx
uses: crazy-max/ghaction-docker-buildx@v1
with:
version: latest

- name: Login to Docker Hub
uses: docker/login-action@v1
with:
registry: ghcr.io
username: ${{ github.repository_owner }}
password: ${{ secrets.GITHUB_TOKEN }}
- name: build (and publish) main image
env:
# fork friendly ^^
DOCKER_REPO: ghcr.io/${{ github.repository_owner }}/endpoints-operator
run: |
docker buildx build \
--platform linux/amd64,linux/arm64 \
--build-arg VERSION=dev \
--push \
-t ${DOCKER_REPO}:dev \
-f Dockerfile \
.
5 changes: 4 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,10 @@ subsets:
protocol: TCP
```

这样手动设置了对应的
这样手动设置了对应的endpoint我们就可以通过service进行访问,但是有个缺点就是如果服务挂掉kube-proxy并检测不到对应的IP是否通讯OK。这个controller主要就是解决这两个问题:

1. 设置cr同步对应的service和endpoint
2. 定时轮训IP如果探针有问题

## Usage

Expand Down