Converting microservice to Knative - istio

Knative is currently in alpha. I need to develop a service, so that when knative is released the conversion is straightforward.
What type of kubernetes deployed service would most easily be converted to knative? I also will be leveraging Istio. So just want to make this as simple as possible. (Also any estimates on when knative will be released or where I should check for that information).

The latest release of Knative, v0.7, is v1beta1 not alpha and as far as I'm aware the API's are now very close to how they will be in v1.0.
We currently use Knative v0.7 and I would suggest developing the apps using that until v1.0 is released.
R.E. Knative v1.0 release, I would keep an eye on these two github milestones: https://github.com/knative/serving/milestone/18 & https://github.com/knative/serving/milestone/24 . The latter milestone is due on August 06 2019 & currently "The ambition of 0.8 [this milestone] is to be a release candidate for a "v1" of serving."

Related

How often do Cloud Build Node.js versions update?

I couldn't stomach purchasing the $150 for GCP's support service for this one question. I'm just looking to understand the schedule for Cloud Build Node.js versions. It's still stuck on Node.js v10.10 and my projects are starting to require higher versions to build. According to Cloud Build's changelog, I don't believe the Node.js version has updated in years. Any ideas?
As per the official Github repository:
Our client libraries follow the Node.js release schedule. Libraries are compatible with all current active and maintenance versions of Node.js.
So, this means it should work with Node.js 12 and the updates should be more constant. In addition to that, in here, it says that if you are using a Cloud Build config file, you can use Node.js 12, so the Node.js' latest version should be compatible with Cloud Build.
To summarize, by the repository, it should follow Node.js schedule. However, in case you think this is not occurring, I would recommend you to raise a bug on the Google's Issue Tracker - it's free, by the way - so they can assess this.

How can I deploy code changes in AWS in a CircleCI 1.0 project?

CircleCI is requiring everyone to migrate to version 2.0 of their configuration format, but I have not had time to move away. I plan to migrate away from the platform anyway, so I do not now wish to migrate to 2.0.
Even after the EOL of 1.0, I was still able to deploy minor code changes, which was all that was necessary to maintain my system at this time.
However, a minor code change I tried to deploy earlier this week failed.
I don't want to migrate to 2.0, but want to deploy the code change (it's 2 lines).
I'm using Github and deploying to AWS.
How I can "circumvent" CircleCI to push this minor code change in Github to AWS?
The 1.0 version was officially "sunsetted" on August 31st, 2018, but I think they might have unofficially given an extension to folks still on 1.0, and it is only now fully being turned off. However, 2.0 has been available for more than a year now, which should have been long enough to do the migration.
My experience of CircleCI support is that if you have a bug, they will help on their forum. Paying customers can log a ticket (and that is a more reliable way to contact them). Of course, if your support issue is to re-enable 1.0, or to do the migration for you, then you do not have a reasonable request.
The trade-off with hosted CI, which will have saved you maintenance time and costs over the long term, is that sometimes migrations will be necessary. Engineering teams should schedule upgrade time into their diary so that these things can be tackled in good time.
Direct answer
For your deployment now, I suggest you run your tests locally and deploy from a development machine. After that, I would suggest upgrading to 2.0 (or move to a different provider) is a high priority for your team.
In other words, I do not believe there is a way in which you can do a deployment using a 1.0 configuration file. However, if you won't move to 2.0, and you do not wish to do a deployment from your own dev machine, you could try asking tech support whether you (or they) can do a special 1.0 run. It is conceivable they still have the capacity to do so.

Is there a successor for Sync Framework 2.1?

we are using Microsoft Sync Framework 2.1 in various customer projects for file and database sync. Extended Support will end in 2021.
So my questions are:
What is Microsofts strategy for the sync framework? Is it going to be open source, so we can change if needed ourselves? Is there a successor product that we should / can migrate to?
Is MSSF supported on Windows 10 and Server 2016?
Not sure if my answer really helps, but lets see: Microsoft announced the official release of the "Azure SQL Data Sync" on June 18 2018. It is not truly a successor of the original framework, but it is basically all you get. Other "non cloud" frameworks have also started to fade away, since Microsoft treats server/desktop/on-premise only as an extension to the cloud. As the name indicates, it is targeting Azure and it is not for file sync, either.
I have seen your question also in the "old" Microsoft social network (social.msdn.microsoft.com/Forums/en-US/home). In there they point to this framework in questions related to the original "Sync Framework" since something like 2012 (this was the oldest question I could associate with both frameworks).

Installation Requirements to Setup PCF on a Local Server

Do you have recommendations to where can I read a good reference on what are the hardware and software requirements, as well as installation procedures of Pivotal Cloud Foundry(not the PCF dev) on a local server?
Links below will get you started.
For PCF on vSphere
http://docs.pivotal.io/pivotalcf/1-8/customizing/vsphere.html
For PCF on Azure
http://docs.pivotal.io/pivotalcf/1-8/customizing/azure.html
For PCF on AWS
http://docs.pivotal.io/pivotalcf/1-8/customizing/cloudform.html
For PCF on GCP
http://docs.pivotal.io/pivotalcf/1-8/customizing/gcp.html
Installing PCF depends on lot of factors. But this is good for an out of the box installation.
PCF is a distributed system, and not designed to be run on a single server. Why do you want to do this? It will not be covered by whatever support agreement you have in place.
PCF Dev is the solution for experimenting with PCF - you can use it as an answer to the question "what is the minimum I need to run PCF", with regards to minimal components and tech specs.

Node.js 0.8.2 on CloudFoundry Micro edition 1.2

The documentation for CloudFoundry indicates that Node.js version 0.8.2 is supported. However, when I run "vmc runtimes" against my local micro edition, it only lists node and node06 (not node08)
I'm running 0.8.2 locally on my box -- how can I upgrade Micro edition so that it also has 0.8.2 installed?
Micro Cloud Foundry 1.2 was released before Node.js 0.8.2 support was added. MCF currently cannot be upgraded to support it. However, a new MCF version is planned for the very near future which will bring parity to all the feature on CloudFoundry.com. We also plan a faster release cadence of MCF so it doesn't fall behind on features.
It's not completely trivial to patch MCF 1.2 to add node 0.8, you'd need to install the relevant packages as well as add information to the Cloud Foundry manifest files to enable it to advertise the node08 runtime.
However, the next Micro Cloud Foundry release should be available pretty soon so if you can hold on just a little longer, we should have some good news for you :-)
Out of interest, what application are you looking to build / run that requires 0.8.x?
Micro Cloud Foundry has just been updated to be in sync with the codebase on github so it now supports Node.js 0.8.2. Read the announcement here: http://blog.cloudfoundry.com/2012/11/08/new-release-of-micro-cloud-foundry/