I was having the same issue as I found here:
#681
So I dug into the dockerfile.
https://github.com/emberstack/kubernetes-reflector/blob/0d074fb01e3f244692a3e257037362ab9454a68f/src/ES.Kubernetes.Reflector/Dockerfile
UBUNTU has been absolutely horrid about supporting FIPS ciphers. I try to avoid them and use alpine or UBI images when possible. I dug into the microsoft ASPNET and the dotnet SDK containers, and Microsoft does release ALPINE based images. Simply using the images literally solves the issue...
FROM mcr.microsoft.com/dotnet/aspnet:10.0-alpine AS base
USER app
WORKDIR /app
EXPOSE 8080
FROM mcr.microsoft.com/dotnet/sdk:10.0.400-alpine3.24-amd64 AS build
ARG BUILD_CONFIGURATION=Release
COPY . .
RUN dotnet build "src/ES.Kubernetes.Reflector/ES.Kubernetes.Reflector.csproj" -c $BUILD_CONFIGURATION
FROM build AS publish
RUN dotnet publish "src/ES.Kubernetes.Reflector/ES.Kubernetes.Reflector.csproj" -c $BUILD_CONFIGURATION -o /app/publish --no-build /p:UseAppHost=false
FROM base AS final
WORKDIR /app
COPY --from=publish /app/publish .
USER 0
RUN chown -R 1654 /app
USER 1654
ENTRYPOINT ["dotnet", "ES.Kubernetes.Reflector.dll"]
I did however, receive a permission error on the /app directory. So I grabbed the username of the default running user, and got their ID and just did a quick CHMOD as root, then switched back to the user:
USER 0
RUN chown -R 1654 /app
USER 1654
This appears to be running happily in my k8s cluster.
I was having the same issue as I found here:
#681
So I dug into the dockerfile.
https://github.com/emberstack/kubernetes-reflector/blob/0d074fb01e3f244692a3e257037362ab9454a68f/src/ES.Kubernetes.Reflector/Dockerfile
UBUNTU has been absolutely horrid about supporting FIPS ciphers. I try to avoid them and use alpine or UBI images when possible. I dug into the microsoft ASPNET and the dotnet SDK containers, and Microsoft does release ALPINE based images. Simply using the images literally solves the issue...
I did however, receive a permission error on the /app directory. So I grabbed the username of the default running user, and got their ID and just did a quick CHMOD as root, then switched back to the user:
This appears to be running happily in my k8s cluster.