service-fabric-on-premises

Service Fabric - How to reserve or protect my hardcoded Port

阅读更多关于 Service Fabric - How to reserve or protect my hardcoded Port

问题 Landscape: We have an Application with two micro services. Micro Service A is used to expose the application outside the cluster (our web server) Micro Service B is our business functionality. We have an F5 in front of Micro Service A to handle the load balancing over the hard coded Ports(onPrem). Inside Micro Service A we are hard coding specific ports for the http endpoint in the manifest. Problem: We witness it is possible that sometimes Micro Service B (Business functionality) will steal

Getting error as part of trying to upgrade Service Fabric Application using Start-ServiceFabricApplicationUpgrade

阅读更多关于 Getting error as part of trying to upgrade Service Fabric Application using Start-ServiceFabricApplicationUpgrade

问题 We got a Service Fabric cluster in our development environment using 2 VMs. I was trying to upgrade the Application deployed in SF using the following command: Start-ServiceFabricApplicationUpgrade -ApplicationName "fabric:/ApplicationName" -ApplicationTypeVersion "3.7.2625.0" -UnMonitoredAuto I get the following error as a result: Start-ServiceFabricApplicationUpgrade : Application type and version not found At line:1 char:1 + Start-ServiceFabricApplicationUpgrade -ApplicationName "fabric:

Dynamic Servicefabric Settings and Overrides

阅读更多关于 Dynamic Servicefabric Settings and Overrides

问题 Is there a way to not tell the service about the settings at all and just provide them at the application level? I am still unhappy with how servicefabric configuration seems to work. Near as I can tell I have to specify in the service’s settings.xml all of the possible configuration values. Then I can override those in the application’s ApplicationParameters. Per documentation this looks like it holds true for environment variables also. The complication that creates is that our

Dynamic Servicefabric Settings and Overrides

阅读更多关于 Dynamic Servicefabric Settings and Overrides

Is there a way to not tell the service about the settings at all and just provide them at the application level? I am still unhappy with how servicefabric configuration seems to work. Near as I can tell I have to specify in the service’s settings.xml all of the possible configuration values. Then I can override those in the application’s ApplicationParameters. Per documentation this looks like it holds true for environment variables also. The complication that creates is that our configuration is used to hydrate options in many cases with arrays. For example consider the json: {