Implantei uma API C# em um cluster Kubernetes
Pelo que entendi, deveríamos ter: GET http request -> Node(30000) -> Pod(80) -> C# API(8080)
Minha imagem docker expõe a porta 8080
FROM our-registry/dotnet/sdk:8.0 AS build
WORKDIR /app
# Copy the project file and restore any dependencies (use .csproj for the project name)
COPY MyApi/MyApi/*.csproj ./
RUN dotnet restore
# Copy the rest of the application code
COPY MyApi/MyApi/. ./
# Publish the application
ARG BUILD_CONFIG=Release
RUN echo "Building with configuration: ${BUILD_CONFIG}"
RUN dotnet publish -c ${BUILD_CONFIG} -o out
# Build the runtime image
FROM our-registry/dotnet/aspnet:8.0 AS runtime
WORKDIR /app
COPY --from=build /app/out ./
# Expose the port your application will run on
EXPOSE 8080
# Start the application
ENTRYPOINT ["dotnet", "MyApi.dll"]
Meu K8 api-service.yaml está definido assim
apiVersion: v1
kind: Service
metadata:
name: my-api-service
namespace: somenamespace
spec:
selector:
app: my-api
ports:
- protocol: TCP
port: 80
targetPort: 8080
nodePort: 30000
type: NodePort
Minhas configurações de inicialização da API C# configuram a porta 8080 e funcionam bem localmente em depuração/lançamento nessa porta
{
"profiles": {
"http": {
"commandName": "Project",
"launchBrowser": true,
"launchUrl": "swagger",
"environmentVariables": {
...
},
"dotnetRunMessages": true,
"applicationUrl": "http://localhost:8080"
},
"https": {
"commandName": "Project",
"launchBrowser": true,
"launchUrl": "swagger",
"environmentVariables": {
...
},
"dotnetRunMessages": true,
"applicationUrl": "https://localhost:7084;http://localhost:8080"
},
...
No cluster, o serviço é executado
kubectl get svc -n somenamespace
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
my-api-service NodePort 10.*.*.* <none> 80:30000/TCP 3h56m
Naquele casulo
kubectl get pods -n somenamespace -o wide
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
my-apipod-*********-***** 1/1 Running 0 138m 10.*.*.* somenode <none> <none>
Eu verifiquei localmente dentro do pod
kubectl exec -it my-apipod-*********-***** -n somenamespace -- bash
...
root@my-apipod-*********-*****:/app# netstat -tulnp | grep LISTEN
tcp 0 0 0.0.0.0:8080 0.0.0.0:* LISTEN 1/dotnet
Obtendo o nó
kubectl get nodes -o wide
NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME
somenode Ready worker 108d v1.28.11+rke2r1 192.168.1.23 192.168.1.23 Ubuntu 20.04.6 LTS 5.4.0-200-generic containerd://1.7.17-k3s1
Tento conectar no ip desse nó com o nodePort 30000
curl -X GET http://192.168.1.23:30000/swagger/index.html -v
Note: Unnecessary use of -X or --request, GET is already inferred.
* Trying 192.168.1.23:30000...
* Connected to 192.168.1.23 (192.168.1.23) port 30000 (#0)
> GET /swagger/index.html HTTP/1.1
> Host: 192.168.1.23:30000
> User-Agent: curl/7.81.0
> Accept: */*
>
* Recv failure: Connection reset by peer
* Closing connection 0
curl: (56) Recv failure: Connection reset by peer
Não tenho certeza do que mais verificar. Executei meu código de API (.NET) localmente e o swagger está funcionando e acessível.
Obrigado pela ajuda
[editar]
Conforme faço solicitações como essas no navegador:
http://192.168.1.23:30000
http://192.168.1.23:30000/swagger/index.html
Nada aparece no log
kubectl logs -f -n mynamespace my-apipod-*********-*****
warn: Microsoft.AspNetCore.Hosting.Diagnostics[15]
Overriding HTTP_PORTS '8080' and HTTPS_PORTS ''. Binding to values defined by URLS instead 'http://0.0.0.0:8080'.
info: Microsoft.Hosting.Lifetime[14]
Now listening on: http://0.0.0.0:8080
info: Microsoft.Hosting.Lifetime[0]
Application started. Press Ctrl+C to shut down.
info: Microsoft.Hosting.Lifetime[0]
Hosting environment: Production
info: Microsoft.Hosting.Lifetime[0]
Content root path: /app
Isso aparece se eu tentar https
warn: Microsoft.AspNetCore.HttpsPolicy.HttpsRedirectionMiddleware[3]
Failed to determine the https port for redirect.
Então a API parece funcionar bem
