Currently there is no easy way to avoid cloud vendor lock-in without compromising: either sacrifice features/functionality, or add cost to maintain several vendor specific variants of their application.

Example of sacrifice: choosing components that are "lowest common denominator", instead of "most suitable". E.g. many problems would be best implemented fine-grained with serverless computing, which is offered as vendor-specific services. Instead, the customer chooses coarse-grain Kubernetes containers because they are supported by all leading clouds; aiming for a "portable solution".

Example of added cost: to configure and operate Kubernetes clusters, vendor specific extensions and services are unavoidable. Before you know it, complexity of the solution is multiplied by number of clouds!

Vendor lock-in is a common concern when adopting cloud services, especially from major hyperscalers like AWS, Azure, and Google Cloud. 

Here are some strategies and tips to mitigate the risk of vendor lock-in:

1. Open Standards and Protocols: Whenever possible, use open standards and protocols. For instance, instead of using a proprietary database, you might opt for an open-source one. This ensures that even if you decide to move away from a particular cloud provider, your data and applications remain accessible.
2. Multi-Cloud Strategy: Design your infrastructure to be portable across multiple cloud providers. This doesn't necessarily mean running everything on multiple clouds simultaneously, but rather ensuring that you can move to another provider with minimal friction if needed.
3. Containers and Kubernetes: Containers encapsulate an application and its dependencies into a single unit, which can be moved easily across environments. Kubernetes, an open-source container orchestration platform, is supported by all major cloud providers, making it easier to migrate containerized applications.
4. Infrastructure as Code (IaC): Tools like Terraform or CloudFormation allow you to define and provision cloud infrastructure using code. By using IaC, you can maintain a level of abstraction and easily replicate your infrastructure on another cloud if necessary.
5. Avoid Proprietary Services: While many cloud-specific services offer convenience and advanced features, they can also tie you to a particular provider. Evaluate the trade-offs before adopting such services.
6. Data Export and Migration Tools: Regularly backup and ensure that you can export your data from the cloud provider. Familiarize yourself with the data migration tools and services offered by cloud providers.
7. Service Brokers: Use service brokers or intermediaries that provide an abstraction layer between your application and the underlying cloud services. This can help in switching between different cloud services without major changes to the application.
8. Negotiate Exit Terms: When entering a contract with a cloud provider, negotiate terms that allow for a smooth exit or transition. This includes understanding data retrieval costs, timelines, and formats.
9. Regularly Review Costs and Services: Cloud ecosystems evolve rapidly. Regularly review the services you're using and their costs. This not only helps in optimizing expenses but also in identifying potential areas of lock-in.
10. Training and Skill Development: One subtle form of lock-in is when your team becomes highly specialized in the tools and services of one provider. Ensure that your team has exposure to tools and services from different providers.
11. Community and Forums: Engage with the community, forums, and user groups. They can provide insights, best practices, and real-world experiences related to vendor lock-in and migration strategies.
12. Proof of Concept (PoC): Before fully committing to a cloud provider, run a PoC to understand the intricacies and potential challenges. This can give you a clearer picture of what a full-scale migration or lock-in might look like.

In conclusion, while it's challenging to completely avoid vendor lock-in in the cloud, a strategic approach can significantly reduce its impact. By planning ahead, using open standards, and regularly reviewing your cloud strategy, you can maintain flexibility and adaptability in your cloud journey.