Legacy Grpc.Core fails on Linux Alpine container about dotnet-etcd

[shubhamranjan]

Thanks for reporting. I will check it out and will plan out the switch to Grpc.Net.Client

[shubhamranjan]

I just need to do some final tests with watch etc and will move to stable once everything seems fine.

[shubhamranjan]

This seems a big change on how certs used to be loaded before. Have already pushed a few changes, should be able to test em and release a new version soon.

[shubhamranjan]

I have tested and released a pre-release version. You may check it out.

Version: 5.0.0-alpha

Thanks !

[baseTwo]

That's fantastic news! I did some testing with it, and it seems to work just fine with .net 5 on Alpine linux. Features used on the client: PutAsync, GetAsync, GetRangeAsync, DeleteAsync and TransactionAsync. Thanks for the quick support! Could you provide a timeline for it to go into a final 5.0.0 version please?

[baseTwo]

I am testing now using certificates, and getting the following exception when creating the EtcdClient whilst specifying the caCert, clientKey and clientCert parameters:

System.InvalidOperationException: SslCredentials with non-null arguments is not supported by GrpcChannel. GrpcChannel uses HttpClient to make gRPC calls and HttpClient automatically loads root certificates from the operating system certificate store. Client certificates should be configured on HttpClient. See https://aka.ms/aspnet/grpc/certauth for details.
at Grpc.Net.Client.Internal.DefaultChannelCredentialsConfigurator.SetSslCredentials(Object state, String rootCertificates, KeyCertificatePair keyCertificatePair, VerifyPeerCallback verifyPeerCallback)
at Grpc.Core.SslCredentials.InternalPopulateConfiguration(ChannelCredentialsConfiguratorBase configurator, Object state)
at Grpc.Net.Client.GrpcChannel..ctor(Uri address, GrpcChannelOptions channelOptions)
at Grpc.Net.Client.GrpcChannel.ForAddress(Uri address, GrpcChannelOptions channelOptions)
at dotnet_etcd.multiplexer.Balancer..ctor(List`1 nodes, String caCert, String clientCert, String clientKey, Boolean publicRootCa)
at dotnet_etcd.EtcdClient..ctor(String connectionString, Int32 port, String caCert, String clientCert, String clientKey, Boolean publicRootCa)
....

It may be possible to configure the client certificates directly on the GrpcChannelOptions.HttpHandler property.

// Add client cert to the handler var handler = new HttpClientHandler(); handler.ClientCertificates.Add(certificate); // Create the gRPC channel var channel = GrpcChannel.ForAddress(baseAddress, new GrpcChannelOptions { HttpHandler = handler });

[baseTwo]

I managed to get a secure connection working by providing the new 5.0.2-alpha EtcdClient constructor with the HttpClientHandler containing the certificates.

[shubhamranjan]

Thanks for the update. Will release a stable version soon.